WELL · 42-349-33864 · DISTRICT 5

Massey #1

Y

Navarro County · Alligator Creek (Sub-Clrksvl.) field · Producing  · Vertical

Massey #1 (API 42-349-33864) is a well in Navarro County operated by Old Union Operating Company, completed April 5, 1985 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued January 14, 1985, permitted to 3,700 ft.

It was permitted by Teco Operating Company and has since transferred to Old Union Operating Company on the wellbore schedule.

Completion filings report 2 formation tops, including Pecan Gap, Austin Chalk.

No lease production has been reported under this well’s leases.

Operator of record

Old Union Operating Company

Permitted by Teco Operating Company; the EWA schedule now lists a different operator.

Austin, TX · P-5 Y, filed Apr 4, 2026 · (800) 906-0486

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOld Union Operating Company
Production reportsOld Union Operating Companythrough Apr 2026
Latest permitTeco Operating CompanyJan 14, 1985

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

3,700
total depth, ft
1
permits on file
Jan 14, 1985
last permit issued
Apr 5, 1985
completed
0
cumulative oil, bbl
190K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 5, 1985
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Massey G-5-116357Alligator Creek (Sub-Clrksvl.)Old Union Operating Company10190KJan 1993 – Jul 2026

Gas, mcf lease total

Last 12 months 2,553 · prior 12 4,811(-47%)

05001K202420252026

Chain of custody

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

  1. 1Teco Operating CompanyJan 1993 → Jun 2001
  2. 2Lehnertz-Faulkner, Inc.Jul 2001 → Apr 2022
  3. 3Old Union Operating CompanyMay 2022 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
264128-99DrillTeco Operating CompanyJan 14, 1985Jan 14, 1985Jan 23, 19853,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-5-116357————

Formation tops

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

FormationMD ftSubsea
Pecan Gap2,250-1,935
Austin Chalk3,180-2,865

Perforations

Perforated and open-hole intervals.

FromToType
3,5863,693Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
7.62534711126 S
4.53,7006.75160 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 17, 1988Sep 19, 1988—
00May 22, 1985May 2, 1985—
00May 21, 1985——

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