WELL · 42-227-31113 · DISTRICT 8
Murray B #9
Howard County · Iatan East Howard field · Injection · Vertical
Murray B #9 (API 42-227-31113) is a well in Howard County operated by Bce-Mach Iii LLC, completed August 29, 2007 and listed as injection on the RRC schedule.
The RRC has issued one drilling permit, issued May 10, 1988, permitted to 2,319 ft.
It was permitted by Chevron U. S. A. Inc. and has since transferred to Bce-Mach Iii LLC on the wellbore schedule.
Completion filings report 3 formation tops, including San Andres, Glorieta, Clear Fork.
Its lease has reported 501K barrels of oil and 17.1K mcf of gas since January 1993, last reporting in July 2026. The lease carries 12 wells, so these are lease totals, not this well alone.
It holds an active disposal or injection permit, with 96.3K barrels injected in the 12 months reported through December 2025.
Operator of record
Permitted by Chevron U. S. A. Inc.; the EWA schedule now lists a different operator.
- Based in
- Oklahoma City, OK
- P-5 status
- Active – Extension (X)
- P-5 last filed
- May 18, 2026
- Permits on file
- 10
- Phone
- (405) 252-8100
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Bce-Mach III LLC |
| Production reports | Bce-Mach III LLCthrough Apr 2026 |
| Latest permit | Chevron U. S. A. Inc.May 10, 1988 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 2,319
- total depth, ft
- 1
- permits on file
- May 10, 1988
- last permit issued
- Aug 29, 2007
- completed
- 501K
- cumulative oil, bbl
- 17.1K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Aug 29, 2007
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active (A)
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; they carry 12 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Murray B O-10-2894 | Iatan, East Howard | Bce-Mach III LLC | 12 | 501K | 17.1K | Jan 1993 – Jul 2026 |
Oil, barrels lease total
Last 12 months 11,129 · prior 12 10,830(+3%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Chevron U. S. A. Inc.Jan 1993 → Aug 2003
- 2Enervest Operating, L.L.C.Sep 2003 → Dec 2005
- 3Energen Resources CorporationJan 2006 → Jan 2019
- 4Diamondback E&P LLCFeb 2019 → Jun 2019
- 5Sabinal Energy Operating, LLCJul 2019 → Aug 2025
- 6Bce-Mach III LLCSep 2025 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 344978-99 | Recompletion | Chevron U. S. A. Inc. | Apr 11, 1988 | May 10, 1988 | — | 3,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Aug 29, 2007 | Murray B O-10-2894 | Iatan East Howard | Bce-Mach III LLC | Injection | 2,319 |
| Jul 11, 1988 | Murray B O-10-2894 | Iatan East Howard | Bce-Mach III LLC | Not on Schedule | — |
| Dec 10, 1976 | Murray -BS- O-10-21691 | Iatan (San Andres) | Bce-Mach III LLC | Not on Schedule | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,261 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| San Andres | 1,548 | 713 |
| San Andres | 1,869 | 392 |
| Glorieta | 2,427 | -166 |
| Clear ForkCLEARFORK | 2,556 | -295 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,391 | 2,803 | Perforated |
| 2,718 | 2,803 | Perforated |
| — | 2,113 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 133 | 13.75 | 125 S |
| 9.625 | 133 | — | 125 S |
| 7 | 2,318 | 8.75 | 525 S |
| 7 | 2,318 | — | 525 S |
| 7 | 2,319 | 8.75 | 525 S |
| 7 | 2,319 | — | 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 | Oct 4, 2024 | Apr 23, 2024 | — |
| 00 | May 14, 1990 | Apr 24, 1990 | — |
| 00 | Aug 15, 1989 | Jul 21, 1989 | — |
| 00 | Aug 1, 1989 | Jul 29, 1988 | Yes |
| 00 | Aug 19, 1988 | Jul 29, 1988 | Yes |
| 00 | Aug 9, 1988 | — | — |
| 00 | Jan 12, 1984 | Dec 22, 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-227-31113 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-227-31113 → 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.
Beyond the permit record
RRC UIC permits · H-10 reported volumes
Injection
- 96.3K
- bbl, last 12 reported months
- 3.89M
- bbl, all reported
- Dec 2025
- reported through
| UIC | Kind | Status | Permitted bbl/d | Max psi | Zone ft |
|---|---|---|---|---|---|
| 000066976 | H-1 Injection | Active | 1,500 | 1,150 | 2,300–2,900 |
MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS
Last 12 months 96,270 · prior 12 131,644(-27%)
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/22731113, documented in the API reference.