TEXAS · WELLS · REEVES COUNTY · BAXTER SPRINGS 54-4-33 LEASE · API 42-389-35672 · DISTRICT 7B
Baxter Springs 54-4-33 #1H
Reeves County · Phantom (Wolfcamp) field · Producing · Horizontal
Baxter Springs 54-4-33 #1H (API 42-389-35672) is a horizontal well in Reeves County operated by Anadarko E&P Onshore LLC, completed March 11, 2023 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued February 1, 2017, permitted to 10,714 ft.
Completion filings report 9 formation tops, including Castile, Permian (undifferentiated), Delaware, Bell Canyon.
Its lease has reported 185K barrels of oil and 2.32M mcf of gas since June 2017, last reporting volume in April 2026.
Operator of record
- Based in
- Houston, TX
- P-5 status
- Active (A)
- P-5 last filed
- Oct 22, 2025
- Permits on file
- 4,576
- Phone
- (713) 215-7000
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Anadarko E&P Onshore LLC |
| Production reports | Anadarko E&P Onshore LLCthrough Apr 2026 |
| Latest permit | Anadarko E&P Onshore LLCFeb 1, 2017 |
- 10,714
- total depth, ft
- 1
- permits on file
- Feb 1, 2017
- last permit issued
- Mar 11, 2023
- completed
- 185K
- cumulative oil, bbl
- 2.32M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Aug 2019 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Mar 11, 2023
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active – Extension (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 |
|---|---|---|---|---|---|---|
| Baxter Springs 54-4-33 G-10-283394 | Phantom (Wolfcamp) | Anadarko E&P Onshore LLC | 1 | 185K | 2.32M | Jun 2017 – Apr 2026 |
Gas, mcf lease total
Last 12 months 138,909 · prior 12 193,233(-28%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Anadarko E&P Onshore LLCAug 2019 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 822176-99 | Drill | Anadarko E&P Onshore LLC | Jan 17, 2017 | Feb 1, 2017 | Mar 5, 2019 | 11,400 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Mar 11, 2023 | Baxter Springs 54-4-33 G-10-283394 | Phantom (Wolfcamp) | Anadarko E&P Onshore LLC | Producing | 10,714 |
Formation tops
As filed on W-2/G-1. Subsea from 2,711 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| CastileCASTILLE | 2,401 | 310 |
| Permian (undifferentiated)PERMIAN | 2,401 | 310 |
| Delaware | 4,131 | -1,420 |
| DelawareFORD-DELAWARE | 4,131 | -1,420 |
| Bell Canyon | 4,156 | -1,445 |
| Cherry Canyon | 5,106 | -2,395 |
| Bone SpringBONE SPRINGS | 7,516 | -4,805 |
| Bone Sptings | 7,516 | -4,805 |
| Wolfcamp | 10,193 | -7,482 |
| DelawareDELAWARE CONSOLIDATED GAS | — | — |
| Pennsylvanian | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 10,881 | 15,130 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 2,158 | 17.5 | 2,140 S |
| 9.625 | 4,241 | 12.25 | 735 S |
| 7 | 10,490 | 8.75 | 842 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jun 15, 2023 | Apr 28, 2023 | — |
| 00 | Feb 13, 2020 | Oct 24, 2019 | Yes |
| 00 | Dec 13, 2019 | Aug 28, 2019 | — |
| 00 | Jun 27, 2019 | Apr 15, 2019 | — |
| 00 | Mar 5, 2018 | Oct 16, 2017 | Yes |
Well logs
1 log loaded from the RRC's log index, 1 of it with a digital LAS file, the latest received Jun 25, 2020. Gamma ray. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| Gamma RaySpans Bone Spring, Bone Sptings, Wolfcamp | LAS + TIFF | 9,473 to 15,294 | Jun 25, 2020 | 0.90 + 5.87 |
"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.
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-389-35672 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-389-35672 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it. The University Lands library has no per-well link: then paste it into its 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/38935672, documented in the API reference.