WELL · 42-337-30138 · DISTRICT 9
Reed, Mae A #1A
Montague County · Vertical
Reed, Mae A #1A (API 42-337-30138) is a permitted well in Montague County filed by Widlake, T. E.; no completion report is on file yet.
The RRC has issued 2 drilling permits in 1984, permitted to 5,400 ft.
Completion filings report 3 formation tops, including Canyon, Brazos River, Caddo.
Its lease has reported 24 barrels of oil and 1 mcf of gas since January 1993, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.
Operator of record
Nocona, TX · P-5 Y, filed Sep 1, 1992 · 8 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | O'Neal, Lindellthrough Jan 1993 |
| Latest permit | Widlake, T. E.Dec 27, 1984 |
- 5,400
- total depth, ft
- 2
- permits on file
- Dec 27, 1984
- last permit issued
- —
- completed
- 24
- cumulative oil, bbl
- 1
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- —
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 |
|---|---|---|---|---|---|---|
| Reed, Mae -A- O-13-4813 | Rogers & Rogers | O'Neal Oil Company | 2 | 24 | 1 | Jan 1993 – Jul 2026 |
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.
- 1O'Neal, LindellJan 1993 → Jan 1993
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 262543-99 | Recompletion | Widlake, T. E. | Dec 17, 1984 | Dec 27, 1984 | — | 5,400 |
| 257708-99 | Recompletion | Widlake, T. E. | Dec 21, 1984 | Nov 12, 1984 | — | 5,400 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-13-4813 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 967 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 4,723 | 4,730 | Perforated |
| — | 2,694 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 7 | 2,750 | 8.75 | 500 S |
| 4.5 | 5,300 | 6.25 | 155 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 | Mar 6, 1986 | Aug 2, 1985 | — |
| 00 | Sep 12, 1985 | Aug 2, 1985 | — |
| 00 | Aug 31, 1985 | — | — |
| 00 | Jan 12, 1984 | — | — |
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-337-30138 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-337-30138 → 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/33730138, documented in the API reference.