WELL · 42-287-31702 · DISTRICT 3

Thessalonians Unit #1

Plugged

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

Thessalonians Unit #1 (API 42-287-31702) is a plugged well in Lee County, plugged March 4, 1996, last operated by Union Pacific Resources Company.

The RRC has issued one drilling permit, issued August 28, 1984, permitted to 8,000 ft.

It was permitted by Perry Oil & Gas Company and has since transferred to Union Pacific Resources Company on the wellbore schedule.

Completion filings report 2 formation tops, including Austin Chalk, Eagle Ford.

Its lease has reported 920 barrels of oil and 5.32K mcf of gas since January 1993, last reporting in August 1996.

Operator of record

Union Pacific Resources Company

Permitted by Perry Oil & Gas Company; the EWA schedule now lists a different operator.

Fort Worth, TX · P-5 Y, filed Feb 9, 2001 · 5,638 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleUnion Pacific Resources Company
Production reportsUnion Pacific Resources Companythrough Mar 1996
Latest permitPerry Oil & Gas CompanyAug 28, 1984

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
1
permits on file
Aug 28, 1984
last permit issued
Sep 28, 1984
completed
920
cumulative oil, bbl
5.32K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Aug 1996

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 28, 1984
Shut in
—
Plugged
Mar 4, 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
Thessalonians Unit O-3-17982Giddings (Austin Chalk-3)Union Pacific Resources Company19205.32KJan 1993 – Aug 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. 1Rim Operating, Inc.Jan 1993 → Nov 1993
  2. 2Gemini Exploration CompanyDec 1993 → Dec 1993
  3. 3Union Pacific Resources CompanyJan 1994 → Mar 1996

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
249927-99DrillPerry Oil & Gas CompanyAug 28, 1984Aug 28, 1984—8,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-17982————

Formation tops

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

FormationMD ftSubsea
Austin Chalk7,007-6,516
Eagle FordEAGLEFORD7,748-7,257

Perforations

Perforated and open-hole intervals.

FromToType
7,6047,748Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,04212.25325 S
5.57,9608.751,300 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 25, 1984Oct 1, 1984—
00Oct 19, 1984——

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