WELL · 42-211-33303 · DISTRICT 10
Bowers D #4
Hemphill County · Washita Creek (Hunton 19475) field · Producing · Vertical
Bowers D #4 (API 42-211-33303) is a well in Hemphill County operated by Kaiser-Francis Oil Company, completed December 19, 2005 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued May 10, 2005, permitted to 19,900 ft.
Completion filings report 6 formation tops, including Morrow, Squaw Belly, Bowers Sd, Chester.
No lease production has been reported under this well’s leases.
Operator of record
Tulsa, OK · P-5 X, filed Apr 15, 2026 · 464 permits on file · (918) 494-0000
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Kaiser-Francis Oil Company |
| Production reports | Kaiser-Francis Oil Companythrough Apr 2026 |
| Latest permit | Kaiser-Francis Oil CompanyMay 10, 2005 |
- 19,900
- total depth, ft
- 1
- permits on file
- May 10, 2005
- last permit issued
- Dec 19, 2005
- completed
- 0
- cumulative oil, bbl
- 10.2M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Sep 2005 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Dec 19, 2005
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: X
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 |
|---|---|---|---|---|---|---|
| Bowers D G-14-216445 | Washita Creek (Hunton 19475) | Kaiser-Francis Oil Company | 1 | 0 | 10.2M | Sep 2005 – Jul 2026 |
Gas, mcf lease total
Last 12 months 473,560 · prior 12 411,735(+15%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Kaiser-Francis Oil CompanySep 2005 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 600409-99 | Drill | Kaiser-Francis Oil Company | May 9, 2005 | May 10, 2005 | May 23, 2005 | 19,900 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-14-216445 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,461 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 19,321 | 19,830 | Open hole |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 20 | 3,530 | 24 | 4,000 S |
| 13.625 | 13,442 | 17.5 | 1,400 S |
| 7 | 19,321 | 8.5 | 300 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 | Oct 23, 2006 | Apr 20, 2006 | Yes |
| 00 | Jun 15, 2006 | — | — |
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-211-33303 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-211-33303 → 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/21133303, documented in the API reference.