WELL · 42-123-32624 · DISTRICT 2

Baros Unit A #1

Plugged

DE Witt County · Eagleville (Eagle Ford-2) field  · Horizontal

Baros Unit A #1 (API 42-123-32624) is a plugged horizontal well in De Witt County, plugged April 17, 2024, last operated by Burlington Resources O & G CO LP.

The RRC has issued one drilling permit (amended once), issued November 1, 2011, permitted to 12,600 ft.

Completion filings report 3 formation tops, including Pecan Gap, Austin Chalk, Eagle Ford.

Its lease has reported 645K barrels of oil and 1.37M mcf of gas since June 2012, last reporting in July 2026. The lease carries 3 wells, so these are lease totals, not this well alone.

Operator of record

Burlington Resources O & G Co LP

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Oct 30, 2025
Permits on file
5,133
Phone
(832) 486-2737

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBurlington Resources O & G Co LP
Production reportsBurlington Resources O & G Co LPthrough Apr 2026
Latest permitBurlington Resources O & G Co LPNov 1, 2011
12,600
total depth, ft
2
permits on file
Nov 1, 2011
last permit issued
Sep 18, 2012
completed
645K
cumulative oil, bbl
1.37M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2012 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 18, 2012
Shut in
—
Plugged
Apr 17, 2024

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Baros Unit A O-2-10215Eagleville (Eagle Ford-2)Burlington Resources O & G Co LP3645K1.37MJun 2012 – Jul 2026

Oil, barrels lease total

Last 12 months 72,408 · prior 12 55,343(+31%)

020K40K202420252026

Gas, mcf lease total

Last 12 months 133,079 · prior 12 80,793(+65%)

020K40K60K202420252026

Chain of custody

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

  1. 1Burlington Resources O & G Co LPNov 2012 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
726386-98DrillBurlington Resources O & G Co LPNov 8, 2012Nov 1, 2011May 28, 201212,600
726386-99DrillBurlington Resources O & G Co LPOct 17, 2011Nov 1, 2011May 28, 201212,600

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-2-10215————

Formation tops

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

FormationMD ftSubsea
Pecan Gap11,559-11,242
Austin Chalk11,739-11,422
Eagle Ford12,144-11,827

Perforations

Perforated and open-hole intervals.

FromToType
12,45018,547Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6253,65912.251,130 S
5.518,7468.752,090 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 5, 2013Jan 30, 2013—
00Dec 14, 2012Oct 11, 2012Yes

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