WELL · 42-167-31272 · DISTRICT 3

Siercovich et al Unit #1

Y

Galveston County · Franks (Schenck Sand) field · Producing  · Vertical

Siercovich ET AL Unit #1 (API 42-167-31272) is a well in Galveston County operated by Orangefield East Corp, completed June 14, 1998 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued May 14, 1996, permitted to 10,950 ft.

It was permitted by El Tres Exploration and has since transferred to Orangefield East Corp on the wellbore schedule.

Its lease has reported 72.8K barrels of oil and 39K mcf of gas since June 1998, last reporting in July 2026.

Operator of record

Orangefield East Corp

Permitted by EL Tres Exploration; the EWA schedule now lists a different operator.

Dallas, TX · P-5 Y, filed Nov 4, 2025 · (972) 256-8289

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOrangefield East Corp
Production reportsOrangefield East Corpthrough Apr 2026
Latest permitEL Tres ExplorationMay 14, 1996

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

10,950
total depth, ft
2
permits on file
May 14, 1996
last permit issued
Jun 14, 1998
completed
72.8K
cumulative oil, bbl
39K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 1998 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jun 14, 1998
Shut in
—
Plugged
—

Operator's P-5 on the schedule: H

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
Siercovich, et al Unit O-3-23537Franks (Schenck Sand)Orangefield East Corp172.8K39KJun 1998 – Jul 2026

Oil, barrels lease total

Last 12 months 460 · prior 12 207(+122%)

05001K202420252026

Chain of custody

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

  1. 1American Discovery Energy IncJun 1998 → Dec 1999
  2. 2Harvest Petroleum Inc.Jan 2000 → Oct 2017
  3. 3Dartex Energy CorporationFeb 2018 → Sep 2023
  4. 4Reo Operating LLCMay 2018 → Aug 2018
  5. 5Lucky Lad Energy, LLCNov 2023 → Jul 2024
  6. 6Orangefield East CorpJan 2026 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
446186-98DrillEL Tres ExplorationOct 31, 1996May 14, 1996Dec 12, 199610,950
446186-99DrillEL Tres ExplorationMar 22, 1996May 14, 1996—10,950

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-23537————

Perforations

Perforated and open-hole intervals.

FromToType
10,76410,774Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6253,95212750 S
5.510,8988.5350 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
00Sep 4, 1998Jul 31, 1998Yes
00Sep 1, 1998——

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