TEXAS · WELLS · OCHILTREE COUNTY · BOMHOFF "D" LEASE · API 42-357-32542 · DISTRICT 08
Bomhoff D #161
Ochiltree County · Farnsworth Se.(morrow Up. Gas) field · Producing · Vertical
Bomhoff D #161 (API 42-357-32542) is a well in Ochiltree County operated by Mewbourne Oil Company, completed April 1, 2006 and listed as producing on the RRC schedule.
The RRC has issued 2 drilling permits (amended once) between 2005 and 2006, permitted to 8,949 ft.
Completion filings report 6 formation tops, including Brown Dolomite, Pennsylvanian, Tonkawa, Cleveland.
Its lease has reported 10.6K barrels of oil and 1.08M mcf of gas since December 2005, last reporting volume in April 2026.
Operator of record
- Based in
- Tyler, TX
- P-5 status
- Active (A)
- P-5 last filed
- May 21, 2026
- Permits on file
- 2,061
- Phone
- (903) 561-2900
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Mewbourne Oil Company |
| Production reports | Mewbourne Oil Companythrough Apr 2026 |
| Latest permit | Mewbourne Oil CompanyMar 23, 2006 |
- 8,949
- total depth, ft
- 3
- permits on file
- Mar 23, 2006
- last permit issued
- Apr 1, 2006
- completed
- 10.6K
- cumulative oil, bbl
- 1.08M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Dec 2005 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Apr 1, 2006
- 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; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Bomhoff "D" G-14-213507 | Farnsworth, Se.(morrow, Up. Gas) | Mewbourne Oil Company | 1 | 10.6K | 1.08M | Dec 2005 – Apr 2026 |
Gas, mcf lease total
Last 12 months 37,321 · prior 12 40,381(-8%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Mewbourne Oil CompanyDec 2005 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 616316-99 | Field transfer | Mewbourne Oil Company | Mar 23, 2006 | Mar 23, 2006 | — | 8,949 |
| 607243-98 | Drill | Mewbourne Oil Company | Oct 25, 2005 | Oct 4, 2005 | Nov 16, 2005 | 9,300 |
| 607243-99 | Drill | Mewbourne Oil Company | Oct 3, 2005 | Oct 4, 2005 | Nov 16, 2005 | 9,300 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Apr 1, 2006 | Bomhoff D G-14-213507 | Farnsworth Se.(morrow Up. Gas) | Mewbourne Oil Company | Producing | 8,949 |
| Apr 1, 2006 | Bomhoff D G-14-213507 | Farnsworth Se.(morrow Up. Gas) | Mewbourne Oil Company | Producing | 8,949 |
Formation tops
As filed on W-2/G-1. Subsea from 3,000 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Brown Dolomite | 3,340 | -340 |
| PennsylvanianPENN SHALE | 4,599 | -1,599 |
| Tonkawa | 6,072 | -3,072 |
| Cleveland | 6,656 | -3,656 |
| Atoka | 7,686 | -4,686 |
| Morrow | 7,957 | -4,957 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 8,030 | 8,040 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,527 | 11 | 555 S |
| 4.5 | 8,949 | 7.875 | 530 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 | Sep 14, 2006 | Mar 29, 2006 | — |
| 00 | May 4, 2006 | Jan 12, 2006 | Yes |
| 00 | Jan 31, 2006 | — | — |
Well logs
2 logs loaded from the RRC's log index, the latest received Dec 12, 2008. Density, Neutron, Resistivity. 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 |
|---|---|---|---|---|
| NEUTRON/DENSITY POROSITYSpans Brown Dolomite, Pennsylvanian, Tonkawa, Cleveland, Atoka, Morrow | TIFF | 3,200 to 8,924 | Dec 12, 2008run Nov 25, 2005 | 13.2 |
| RESISTIVITYSpans Brown Dolomite, Pennsylvanian, Tonkawa, Cleveland, Atoka, Morrow | TIFF | 1,518 to 8,934 | Dec 12, 2008run Nov 25, 2005 | 13.6 |
"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-357-32542 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-357-32542 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it.
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/35732542, documented in the API reference.