WELL · 42-051-32860 · DISTRICT 3

Buckman #1

Plugged

Burleson County · Caldwell NE (Georgetown) field  · Vertical

Buckman #1 (API 42-051-32860) is a plugged well in Burleson County, plugged September 19, 1995, last operated by T & T Production CO..

The RRC has issued 2 drilling permits between 1985 and 1993, permitted to 8,000 ft.

Completion filings report 2 formation tops, including Chalk, Buda.

Its 2 leases have reported 1.22K barrels of oil and 31 mcf of gas since January 1993, last reporting in January 1996. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

T & T Production Co.

Victoria, TX · P-5 Y, filed Dec 2, 1994 · 23 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleT & T Production Co.
Production reportsDelaware Ecco Petroleum Inc.through Jun 1995
Latest permitT & T Production Co.Nov 22, 1993

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

8,000
total depth, ft
2
permits on file
Nov 22, 1993
last permit issued
Jul 15, 1985
completed
1.22K
cumulative oil, bbl
31
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jan 1996

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 15, 1985
Shut in
—
Plugged
Sep 19, 1995

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Buckman O-3-22291Caldwell (Austin Chalk)Delaware Ecco Petroleum Inc.168918Dec 1993 – Jan 1996
Buckman O-3-19336Caldwell, NE (Georgetown)T & T Production Co.152913Jan 1993 – Apr 1994

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.

  1. 1T & T Production Co.Jan 1993 → Feb 1995
  2. 2Delaware Ecco Petroleum Inc.Mar 1995 → Jun 1995

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
418423-99RecompletionT & T Production Co.Nov 18, 1993Nov 22, 1993Dec 9, 19938,000
278101-99DrillT & T Production Co.Aug 20, 1986Jun 19, 1985—8,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-19336————
—— O-3-22291————

Formation tops

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

FormationMD ftSubsea
Chalk6,660-6,389
Buda7,190-6,919

Perforations

Perforated and open-hole intervals.

FromToType
6,6656,725Perforated
7,1907,220Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
5.5737.875395 S
8.6253,25012.25790 S
5.57,3707.875—

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
00Mar 11, 1994Jan 13, 1994Yes
00Mar 4, 1994May 8, 1986—
00Sep 8, 1986May 8, 1986—
00Sep 4, 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/05132860, documented in the API reference.