WELL · 42-201-31043 · DISTRICT 3
White #10
Harris County · Fairbanks (Cockfield 6500) field · Vertical
White #10 (API 42-201-31043) is a plugged well in Harris County, plugged May 1, 2003, last operated by Pringle Resources Inc..
The RRC has issued 2 drilling permits between 1980 and 1981, permitted to 8,000 ft.
It was permitted by Pringle Petroleum, Inc. and has since transferred to Pringle Resources Inc. on the wellbore schedule.
Operator of record
Permitted by Pringle Petroleum, Inc.; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Inactive (I)
- P-5 last filed
- May 21, 2007
- Permits on file
- 15
- Phone
- (713) 651-1130
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Houston Expl. & Prod. Co., Inc.through Aug 1993 |
| Latest permit | Pringle Petroleum, Inc.May 1, 1981 |
- 8,000
- total depth, ft
- 2
- permits on file
- May 1, 1981
- last permit issued
- Apr 9, 1981
- completed
- 0
- cumulative oil, bbl
- 19.5K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2003
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Apr 9, 1981
- Shut in
- —
- Plugged
- May 1, 2003
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 |
|---|---|---|---|---|---|---|
| White G-3-93111 | Fairbanks (Cockfield 6500) | Pringle Resources, Inc. | 1 | 0 | 19.5K | Jan 1993 – Jul 2003 |
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.
- 1Houston Expl. & Prod. Co., Inc.Jan 1993 → Aug 1993
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 116821-99 | Recompletion | Pringle Petroleum, Inc. | May 1, 1981 | May 1, 1981 | — | 7,816 |
| 80529-99 | Drill | Pringle Petroleum, Inc. | May 5, 1980 | May 5, 1980 | — | 8,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Apr 9, 1981 | White G-3-93111 | Fairbanks (Cockfield 6500) | Pringle Resources Inc. | Plugged | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 6,488 | 6,509 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,260 | 12.5 | 490 S |
| 2.375 | 6,463 | — | — |
| 5.5 | 7,611 | 7.875 | 573 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 | Apr 20, 1981 | — |
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-201-31043 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-201-31043 → 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/20131043, documented in the API reference.