WELL · 42-001-32543 · DISTRICT 6
McGee #1
Anderson County · Isaac Lindsey (Pettit) field · Vertical
Mcgee #1 (API 42-001-32543) is a plugged well in Anderson County, plugged November 11, 2012, last operated by J-W Operating CO..
The RRC has issued one drilling permit (amended once), issued November 16, 2006, permitted to 15,000 ft.
Completion filings report 7 formation tops, including Wdbn, Tma, BMA, Rdss.
Its lease has reported 918 barrels of oil since March 2007, last reporting in December 2012.
Operator of record
- Based in
- Addison, TX
- P-5 status
- Delinquent (D)
- P-5 last filed
- Jul 30, 2019
- Permits on file
- 350
- Phone
- (972) 233-8191
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | J-W Operating Co. |
| Production reports | J-W Operating Co.through Feb 2008 |
| Latest permit | J-W Operating Co.Nov 16, 2006 |
- 15,000
- total depth, ft
- 2
- permits on file
- Nov 16, 2006
- last permit issued
- Mar 24, 2007
- completed
- 918
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Mar 2007 THROUGH Dec 2012
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Mar 24, 2007
- Shut in
- —
- Plugged
- Nov 11, 2012
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 |
|---|---|---|---|---|---|---|
| McGee O-6-14653 | Isaac Lindsey (Pettit) | J-W Operating Co. | 1 | 918 | 0 | Mar 2007 – Dec 2012 |
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.
- 1J-W Operating Co.Apr 2007 → Feb 2008
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 629089-98 | Drill | J-W Operating Co. | Mar 1, 2007 | Nov 16, 2006 | Dec 15, 2006 | 15,000 |
| 629089-99 | Drill | J-W Operating Co. | Nov 15, 2006 | Nov 16, 2006 | Dec 15, 2006 | 15,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-6-14653 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 454 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 10,516 | 10,526 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 2,245 | 12.25 | 857 S |
| 5.5 | 10,720 | 7.875 | 661 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 | Jun 27, 2007 | May 1, 2007 | Yes |
| 00 | Jun 25, 2007 | — | — |
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-001-32543 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-001-32543 → 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/00132543, documented in the API reference.