WELL · 42-007-00935 · DISTRICT 4
Texas State Tract 143 #1
Aransas County · Vertical
Texas State Tract 143 #1 (API 42-007-00935) is a permitted well in Aransas County filed by Getty Oil CO.; no completion report is on file yet.
The RRC has issued one drilling permit, issued April 25, 1984, permitted to 11,936 ft.
Operator of record
- Based in
- Midland, TX
- P-5 status
- Inactive (I)
- P-5 last filed
- Mar 27, 1989
- Permits on file
- 1,564
- Phone
- (432) 688-4100
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Petro-Hunt, L.L.C.through Sep 2012 |
| Latest permit | Getty Oil Co.Apr 25, 1984 |
- 11,936
- total depth, ft
- 1
- permits on file
- Apr 25, 1984
- last permit issued
- —
- completed
- 0
- cumulative oil, bbl
- 1.98M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Oct 2012
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; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Texas State Tract 143 G-4-45176 | Nine Mile Point (Consol. Fld.) | Petro-Hunt, L.L.C. | 1 | 0 | 1.98M | Jan 1993 – Oct 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.
- 1Texaco E & P Inc.Jan 1993 → Nov 1994
- 2Petro-Hunt CorporationDec 1994 → Oct 1998
- 3Petro-Hunt, L.L.C.Nov 1998 → Sep 2012
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 236655-99 | Recompletion | Getty Oil Co. | Apr 18, 1984 | Apr 25, 1984 | — | 11,936 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-4-45176 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 10,456 | 10,904 | Perforated |
| 10,606 | 10,619 | Perforated |
| 10,734 | 10,753 | Perforated |
| 10,840 | 10,862 | Perforated |
| 10,868 | 10,904 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 16 | 150 | — | — |
| 10.75 | 1,516 | 15 | 820 S |
| 7.625 | 9,092 | 9.875 | — |
| 7.625 | 9,171 | 9.875 | 367 S |
| 7.625 | 9,180 | 9.875 | 205 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 24, 1994 | Nov 16, 1993 | — |
| 00 | Nov 14, 1989 | Oct 13, 1989 | — |
| 00 | Jan 5, 1989 | Nov 10, 1988 | — |
| 00 | Jan 12, 1984 | Dec 18, 1968 | — |
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-007-00935 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-007-00935 → 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/00700935, documented in the API reference.