WELL · 42-029-37272 · DISTRICT 1

Haggard -BRS- #5

Y

Bexar County · Fairfield field · Producing  · Vertical

Haggard -Brs- #5 (API 42-029-37272) is a well in Bexar County operated by Haggard Operating Group/Oil, completed March 8, 1986 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued February 12, 1986, permitted to 860 ft.

It was permitted by Monroe Well Service, Inc. and has since transferred to Haggard Operating Group/Oil on the wellbore schedule.

Completion filings report one formation top, including Escondido.

Its lease has reported 2.15K barrels of oil and 179 mcf of gas since January 1993, last reporting in July 2026. The lease carries 17 wells, so these are lease totals, not this well alone.

Operator of record

Haggard Operating Group/Oil

Permitted by Monroe Well Service, Inc.; the EWA schedule now lists a different operator.

Atascosa, TX · P-5 Y, filed Aug 4, 2025 · (210) 622-3886

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHaggard Operating Group/Oil
Production reportsHaggard Operating Group/Oilthrough Apr 2026
Latest permitMonroe Well Service, Inc.Feb 12, 1986

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

860
total depth, ft
1
permits on file
Feb 12, 1986
last permit issued
Mar 8, 1986
completed
2.15K
cumulative oil, bbl
179
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 8, 1986
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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 17 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Haggard -BRS- O-1-11444FairfieldHaggard Operating Group/Oil172.15K179Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 12 · prior 12 12(+0%)

01202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Haggard Operating Group/OilMay 1993 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
297610-99DrillMonroe Well Service, Inc.Feb 12, 1986Feb 12, 1986—860

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-11444————

Formation tops

As filed on W-2/G-1. Subsea from 631 ft elevation.Download CSV →

FormationMD ftSubsea
Escondido425206

Perforations

Perforated and open-hole intervals.

FromToType
679683Perforated
701703Perforated
715719Perforated
724729Perforated
733735Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.58486.75124 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 →

SuffixFiledW-2 / G-1 dateLogs referenced
00Apr 17, 1986Apr 4, 1986Yes
00Apr 15, 1986——

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.

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/02937272, documented in the API reference.