WELL · 42-237-31940 · DISTRICT 9
Tucker J. M. #1
Jack County · Newport S. (Bend Congl.) field · Producing · Vertical
Tucker J. M. #1 (API 42-237-31940) is a well in Jack County operated by Cary Oil & Gas Inc, completed September 1, 1977 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued July 27, 1977, permitted to 7,000 ft.
It was permitted by Eagle Oil & Gas CO. and has since transferred to Cary Oil & Gas Inc on the wellbore schedule.
No lease production has been reported under this well’s leases.
Operator of record
Permitted by Eagle Oil & Gas Co.; the EWA schedule now lists a different operator.
Decatur, TX · P-5 Y, filed Mar 4, 2026 · 4 permits on file · (940) 627-1241
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Cary Oil & Gas Inc |
| Production reports | Cary Oil & Gas, Incthrough Apr 2026 |
| Latest permit | Eagle Oil & Gas Co.Jul 27, 1977 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 7,000
- total depth, ft
- 1
- permits on file
- Jul 27, 1977
- last permit issued
- Sep 1, 1977
- completed
- 0
- cumulative oil, bbl
- 229K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Sep 1, 1977
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active
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; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Tucker, J. M. G-13-72693 | Newport, S. (Bend Congl.) | Cary Oil & Gas, Inc | 1 | 0 | 229K | Jan 1993 – Jul 2026 |
Gas, mcf lease total
Last 12 months 5,454 · prior 12 2,720(+101%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Eagle Oil & Gas Co.Jan 1993 → Dec 1999
- 2Pruitt Oil & GasJan 2000 → Dec 2015
- 3Cary Oil & Gas, IncJan 2016 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 1208-99 | Drill | Eagle Oil & Gas Co. | Jul 27, 1977 | Jul 27, 1977 | Jul 5, 1977 | 7,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-13-72693 | — | — | — | — |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 523 | 12.25 | 370 S |
| 4.5 | 6,091 | 7.875 | 300 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 | Sep 12, 1977 | — |
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-237-31940 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-237-31940 → 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/23731940, documented in the API reference.