WELL · 42-221-30599 · DISTRICT 7
Black Ranch 471 #4
Hood County · Black Ranch (Atoka 800) field · Vertical
Black Ranch 471 #4 (API 42-221-30599) is a well in Hood County operated by E.G. Operating, completed May 16, 1980.
The RRC has issued one drilling permit, issued February 14, 1980, permitted to 1,562 ft.
It was permitted by Stallworth Oil & Gas, Inc and has since transferred to E.G. Operating on the wellbore schedule.
No lease production has been reported under this well’s leases.
Operator of record
Permitted by Stallworth Oil & Gas, Inc; the EWA schedule now lists a different operator.
Dallas, TX · P-5 Y, filed Sep 6, 2002 · 72 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | E.G. Operating |
| Production reports | E.G. Operatingthrough Jul 1994 |
| Latest permit | Stallworth Oil & Gas, IncFeb 14, 1980 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 1,562
- total depth, ft
- 1
- permits on file
- Feb 14, 1980
- last permit issued
- May 16, 1980
- completed
- 0
- cumulative oil, bbl
- 963
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 1994
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- May 16, 1980
- 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 |
|---|---|---|---|---|---|---|
| Black Ranch 471 G-8-90888 | Black Ranch (Atoka 800) | E.G. Operating | 1 | 0 | 963 | Jan 1993 – Jul 1994 |
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.
- 1Lynx Energy Company, Inc.Jan 1993 → Mar 1993
- 2E.G. OperatingApr 1993 → Jul 1994
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 72971-99 | Drill | Stallworth Oil & Gas, Inc | Feb 14, 1980 | Feb 14, 1980 | Feb 18, 1980 | 1,562 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-8-90888 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 755 | 766 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 285 | 12.25 | 175 S |
| 2.375 | 723 | — | — |
| 4.5 | 1,033 | 7.875 | 525 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 25, 1980 | — |
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-221-30599 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-221-30599 → 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/22130599, documented in the API reference.