WELL · 42-399-32561 · DISTRICT 7
Eager Clarence #2
Runnels County · Morrison (Fry) field · Vertical
Eager Clarence #2 (API 42-399-32561) is a plugged well in Runnels County, plugged July 28, 1995, last operated by Morrison Drlg. & Prod. CO. Inc..
The RRC has issued one drilling permit, issued September 15, 1982, permitted to 5,000 ft.
Its lease has reported 260 barrels of oil and 12 mcf of gas since January 1993, last reporting in September 1995. The lease carries 2 wells, so these are lease totals, not this well alone.
Operator of record
Morrison Drlg. & Prod. Co. Inc.
- Based in
- Abilene, TX
- P-5 status
- Inactive (I)
- P-5 last filed
- Aug 8, 2003
- Permits on file
- 47
- Phone
- (325) 698-1161
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Morrison Drlg. & Prod. Co. Inc. |
| Production reports | Morrison Drlg. & Prod. Co., Inc.through Apr 1994 |
| Latest permit | Morrison Drlg. & Prod. Co., Inc.Sep 15, 1982 |
- 5,000
- total depth, ft
- 1
- permits on file
- Sep 15, 1982
- last permit issued
- Nov 18, 1982
- completed
- 260
- cumulative oil, bbl
- 12
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Sep 1995
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Nov 18, 1982
- Shut in
- —
- Plugged
- Jul 28, 1995
Surface location
No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.
Lease production
PDQ LEASE REPORTS · REPORTED THROUGH APR 2026
Texas reports oil by lease, not by well. These are the lease this well is completed on; they carry 2 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Eager, Clarence O-9-9904 | Morrison (Fry) | Morrison Drlg. & Prod. Co., Inc. | 2 | 260 | 12 | Jan 1993 – Sep 1995 |
No volumes reported on these leases in the last three years.
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Gallaway, W. M.Jan 1993 → Apr 1993
- 2Morrison Drlg. & Prod. Co., Inc.May 1993 → Mar 1994
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 171940-99 | Drill | Morrison Drlg. & Prod. Co., Inc. | Sep 15, 1982 | Sep 15, 1982 | — | 5,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-9-9904 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 4,374 | 4,382 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 202 | 12.25 | 250 S |
| 2.375 | 4,412 | — | — |
| 4.5 | 4,602 | 7.875 | 150 S |
Completion filings
W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jan 12, 1984 | Nov 30, 1982 | — |
The source documents
Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.
- Wellbore filings for 42-399-32561 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-399-32561 → scanned completion filings
Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.
About this data
Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.
New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease
Developers: this page as JSON is GET /v1/data/wells/39932561, documented in the API reference.