WELL · 42-123-32613 · DISTRICT 2

Lackey Land a 639 Unit A #1

Y

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

Lackey Land A 639 Unit A #1 (API 42-123-32613) is a horizontal well in De Witt County operated by Burlington Resources O & G CO LP, completed August 16, 2013 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued October 13, 2011, permitted to 13,300 ft.

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

Its lease has reported 396K barrels of oil and 1.02M mcf of gas since August 2012, last reporting in July 2026. The lease carries 2 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 Mar 2026
Latest permitBurlington Resources O & G Co LPOct 13, 2011
13,300
total depth, ft
1
permits on file
Oct 13, 2011
last permit issued
Aug 16, 2013
completed
396K
cumulative oil, bbl
1.02M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2012 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 16, 2013
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 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Lackey Land a 639 Unit A O-2-10188Eagleville (Eagle Ford-2)Burlington Resources O & G Co LP2396K1.02MAug 2012 – Jul 2026

Gas, mcf lease total

Last 12 months 4,236 · prior 12 10,502(-60%)

02K4K6K202420252026

Oil, barrels lease total

Last 12 months 432 · prior 12 1,174(-63%)

0200400202420252026

Chain of custody

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

  1. 1Burlington Resources O & G Co LPAug 2012 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
725992-99DrillBurlington Resources O & G Co LPOct 10, 2011Oct 13, 2011Mar 31, 201213,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-2-10188————

Formation tops

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

FormationMD ftSubsea
Pecan Gap12,416-12,005
Austin Chalk12,617-12,206
Eagle Ford12,954-12,543

Perforations

Perforated and open-hole intervals.

FromToType
13,49818,784Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6253,64712.251,270 S
5.518,9748.752,050 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
00Jan 2, 2014Oct 14, 2013—
00Nov 26, 2012Sep 28, 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/12332613, documented in the API reference.