WELL · 42-325-31810 · DISTRICT 1
Barr M.B. #1
Medina County · Chicon Lake field · Vertical
Barr M.B. #1 (API 42-325-31810) is a plugged well in Medina County, plugged March 26, 1999, last operated by S & H Gutierrez.
The RRC has issued one drilling permit, issued June 26, 1981, permitted to 750 ft.
It was permitted by M C Drilling CO., Inc. and has since transferred to S & H Gutierrez on the wellbore schedule.
Its lease has reported 281 barrels of oil and 100 mcf of gas since January 1993, last reporting in July 2026. The lease carries 6 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by M C Drilling Co., Inc.; the EWA schedule now lists a different operator.
Lytle, TX · P-5 Y, filed Jul 4, 2026 · (210) 777-6617
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | S & H Gutierrez |
| Production reports | M B Oilthrough Feb 2021 |
| Latest permit | M C Drilling Co., Inc.Jun 26, 1981 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 750
- total depth, ft
- 1
- permits on file
- Jun 26, 1981
- last permit issued
- Jul 17, 1981
- completed
- 281
- cumulative oil, bbl
- 100
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jul 17, 1981
- Shut in
- —
- Plugged
- Mar 26, 1999
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 6 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Barr, M.B. O-1-7683 | Chicon Lake | S & H Gutierrez | 6 | 281 | 100 | Jan 1993 – Jul 2026 |
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.
- 1M B OilJan 1993 → Feb 2021
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 123259-99 | Drill | M C Drilling Co., Inc. | Jun 26, 1981 | Jun 26, 1981 | Jul 8, 1981 | 750 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-1-7683 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 455 | 460 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 2 | 433 | — | — |
| 4.5 | 485 | — | — |
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 | Jan 19, 1982 | — |
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-325-31810 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-325-31810 → 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/32531810, documented in the API reference.