WELL · 42-051-31319 · DISTRICT 3

Payne Thomas A. #1

Plugged

Burleson County · Giddings (Austin Chalk-3) field  · Vertical

Payne Thomas A. #1 (API 42-051-31319) is a plugged well in Burleson County, plugged June 20, 1996, last operated by Union Pacific Resources Company.

The RRC has issued 2 drilling permits between 1981 and 1989, permitted to 7,850 ft.

Completion filings report 4 formation tops, including Austin Chalk, False Buda, Buda, Georgetown.

Its lease has reported 7.47K barrels of oil and 202 mcf of gas since January 1993, last reporting in July 1996.

Operator of record

Union Pacific Resources Company

Based in
Fort Worth, TX
P-5 status
Inactive (I)
P-5 last filed
May 2, 2000
Permits on file
5,638
Phone
(817) 321-7424

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleUnion Pacific Resources Company
Production reportsUnion Pacific Resources Companythrough Nov 1994
Latest permitUnion Pacific Resources CompanyMar 31, 1989
7,850
total depth, ft
2
permits on file
Mar 31, 1989
last permit issued
Aug 30, 1989
completed
7.47K
cumulative oil, bbl
202
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 1996

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 30, 1989
Shut in
—
Plugged
Jun 20, 1996

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Payne, Thomas A. O-3-13977Giddings (Austin Chalk-3)Union Pacific Resources Company17.47K202Jan 1993 – Jul 1996

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. 1Union Pacific Resources CompanyJan 1993 → Nov 1994

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
357658-99RecompletionUnion Pacific Resources CompanyMar 31, 1989Mar 31, 1989—7,570
107259-99DrillChamplin Petroleum Co.Feb 2, 1981Feb 2, 1981—7,850

Completions

CompletedLeaseFieldOperatorStatusDepth
Aug 30, 1989Payne Thomas A. O-3-13977Giddings (Austin Chalk-3)Union Pacific Resources CompanyPlugged—
Aug 30, 1989Payne Thomas A. O-3-13977Giddings (Austin Chalk-3)Union Pacific Resources CompanyPlugged—

Formation tops

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

FormationMD ftSubsea
Austin Chalk6,825-6,535
False Buda7,259-6,969
Buda7,306-7,016
Georgetown7,376-7,086

Perforations

Perforated and open-hole intervals.

FromToType
6,8566,938Perforated
7,3107,350Perforated
7,3847,454Perforated
7,4747,510Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6253,51212.251,350 S
2.3756,766——
5.57,5708.75550 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
00Oct 12, 1989Sep 8, 1989Yes
00Jan 12, 1984Mar 24, 1981—

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