WELL · 42-355-33400 · DISTRICT 4

State Tract 61 Temporary Unit #1

Plugged

Nueces County · Marina (11200) field  · Directional

State Tract 61 Temporary Unit #1 (API 42-355-33400) is a plugged well in Nueces County, plugged April 4, 2015, last operated by White Marlin Operating CO LLC.

The RRC has issued 2 drilling permits between 2001 and 2002, permitted to 16,000 ft.

It was permitted by Sabco Operating Company and has since transferred to White Marlin Operating CO LLC on the wellbore schedule.

Completion filings report one formation top, including Anderson.

Operator of record

White Marlin Operating Co LLC

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

Houston, TX · P-5 Y, filed Nov 4, 2025 · 32 permits on file · (713) 935-2325

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWhite Marlin Operating Co LLC
Production reportsWhite Marlin Operating Co, LLCthrough Feb 2014
Latest permitSabco Operating CompanyAug 30, 2002

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

16,000
total depth, ft
2
permits on file
Aug 30, 2002
last permit issued
Sep 22, 2001
completed
0
cumulative oil, bbl
5.69M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2001 THROUGH Apr 2015

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 22, 2001
Shut in
—
Plugged
Apr 4, 2015

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
State Tract 61 Temporary Unit G-4-185577Marina (11200)White Marlin Operating Co, LLC105.69MSep 2001 – Apr 2015

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. 1Sabco Operating CompanySep 2001 → Oct 2011
  2. 2Sabco Operating Company, LLCDec 2011 → Jan 2014
  3. 3White Marlin Operating Co, LLCFeb 2014 → Feb 2014

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
523288-99Field transferSabco Operating CompanyAug 30, 2002Aug 30, 2002Jun 18, 200116,000
511345-99DrillSabco Operating CompanyJul 12, 2001Jul 12, 2001Jun 18, 200116,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-185577————

Formation tops

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

FormationMD ftSubsea
Anderson——

Perforations

Perforated and open-hole intervals.

FromToType
11,20611,216Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.8752,50017.51,730 S
9.6259,96012.25505 S
711,5938.5233 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 9, 2002Sep 16, 2002—
00Dec 17, 2001Nov 5, 2001Yes
00Nov 27, 2001——

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