WELL · 42-071-00896 · DISTRICT 3

Troy Casey Unit #1

Plugged

Chambers County · Petkas (Frio 8170) field  · Vertical

Troy Casey Unit #1 (API 42-071-00896) is a plugged well in Chambers County, plugged September 27, 2010, last operated by Schnapp Ben H..

The RRC has issued 2 drilling permits between 1984 and 1986, permitted to 8,300 ft.

It was permitted by Goldking Prod. CO. and has since transferred to Schnapp Ben H. on the wellbore schedule.

Its lease has reported 60.1K barrels of oil and 28.6K mcf of gas since January 1993, last reporting in March 2023.

Operator of record

Schnapp Ben H.

Permitted by Goldking Prod. Co.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Aug 14, 1987

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSchnapp Ben H.
Production reportsRotation, Incorporatedthrough Dec 2006
Latest permitGoldking Prod. Co.Jan 3, 1986

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

8,300
total depth, ft
2
permits on file
Jan 3, 1986
last permit issued
Dec 1, 1967
completed
60.1K
cumulative oil, bbl
28.6K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2023

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 1, 1967
Shut in
—
Plugged
Sep 27, 2010

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
Casey, Troy O-3-19840Petkas (Frio 7650)Rotation, Incorporated160.1K28.6KJan 1993 – Mar 2023

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. 1Denovo Oil & Gas, Inc.Jan 1993 → Apr 1994
  2. 2Lomak Production CompanyMay 1994 → Sep 1997
  3. 3Engroup Resources, L.P.Oct 1997 → Jan 2002
  4. 4Rotation, IncorporatedFeb 2002 → Dec 2006

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
294817-99RecompletionGoldking Prod. Co.Nov 20, 1985Jan 3, 1986—8,300
235975-99RecompletionGoldking Prod. Co.Mar 2, 1984Apr 13, 1984—8,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-19840————

Perforations

Perforated and open-hole intervals.

FromToType
7,2387,240Perforated
7,4867,488Perforated
7,6467,649Perforated
7,7537,756Perforated
8,1518,154Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.625600——
9.62560010.75—
2.3758,170——
5.58,3108.75610 sx
5.58,310——

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
00Dec 2, 1987Oct 14, 1987—
00Nov 21, 1987——
00Feb 7, 1986Jan 25, 1986—
00Feb 5, 1986——
00Jun 20, 1984May 4, 1984Yes
00Jun 8, 1984May 4, 1984—
00Jan 12, 1984Jun 29, 1976—
00Jan 12, 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/07100896, documented in the API reference.