WELL · 42-371-31620 · DISTRICT 8
Wimberly - Bryan #2
Pecos County · Puckett North (Strawn Detrital) field · Vertical
Wimberly - Bryan #2 (API 42-371-31620) is a permitted well in Pecos County filed by Highland Resources, Inc.; no completion report is on file yet.
The RRC has issued one drilling permit, issued October 27, 1982, permitted to 14,983 ft.
Operator of record
Houston, TX · P-5 Y, filed Mar 17, 1986 · 62 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Highland Resources Inc. |
| Production reports | Sahara Operating Companythrough Feb 2016 |
| Latest permit | Highland Resources, Inc.Oct 27, 1982 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 14,983
- total depth, ft
- 1
- permits on file
- Oct 27, 1982
- last permit issued
- —
- completed
- 0
- cumulative oil, bbl
- 195K
- 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; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Wimberly-Bryan G-10-103312 | Puckett, North (Penn Lime) | Sahara Operating Company | 1 | 0 | 195K | 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.
- 1Brown, George R. Partnership,theJan 1993 → May 1996
- 2Engroup Resources, L.P.Jun 1996 → Sep 2000
- 3Finley Resources, Inc.Oct 2000 → Nov 2011
- 4Sahara Operating CompanyDec 2011 → Feb 2016
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 175589-99 | Drill | Highland Resources, Inc. | Oct 27, 1982 | Oct 27, 1982 | — | 14,983 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-10-103312 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 9,317 | 9,520 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 3,293 | 12.25 | 1,870 S |
| 2.875 | 9,204 | — | — |
| 2.875 | 9,532 | — | — |
| 7.625 | 10,000 | 8.5 | 500 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 | Nov 29, 1982 | — |
| 00 | Jan 12, 1984 | Aug 24, 1976 | — |
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-371-31620 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-371-31620 → scanned completion filings
Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward) and the University Lands library. 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/37131620, documented in the API reference.