WELL · 42-429-33308 · DISTRICT 7

Scarlett A #A2

Plugged

Stephens County · Stephens County Regular field  · Vertical

Scarlett A #A2 (API 42-429-33308) is a plugged well in Stephens County, plugged April 22, 2011, last operated by Ray Herring Operating CO. LLC.

The RRC has issued 2 drilling permits in 1982, permitted to 4,400 ft.

It was permitted by Herring, Ray and has since transferred to Ray Herring Operating CO. LLC on the wellbore schedule.

Completion filings report 2 formation tops, including Caddo, Conglomerate.

Its lease has reported 1.8K barrels of oil and 4.08K mcf of gas since January 1993, last reporting in March 2024.

Operator of record

Ray Herring Operating Co. LLC

Permitted by Herring, Ray; the EWA schedule now lists a different operator.

Graham, TX · P-5 Y, filed Dec 4, 2025 · 8 permits on file · (940) 550-8988

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRay Herring Operating Co. LLC
Production reportsHerring, Raythrough Apr 2011
Latest permitHerring, RayOct 15, 1982

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

4,400
total depth, ft
2
permits on file
Oct 15, 1982
last permit issued
Mar 28, 2010
completed
1.8K
cumulative oil, bbl
4.08K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2024

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 28, 2010
Shut in
—
Plugged
Apr 22, 2011

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
Scarlett "A" O-8-17634Stephens County RegularRay Herring Operating Co., LLC11.8K4.08KJan 1993 – Mar 2024

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. 1Herring, RayJan 1993 → Apr 2011

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
174462-99RecompletionHerring, RayOct 15, 1982Oct 15, 1982—3,600
161241-99DrillHerring, RayMay 20, 1982May 20, 1982—4,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-17634————

Formation tops

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

FormationMD ftSubsea
Caddo3,487-2,093
Conglomerate3,709-2,315

Perforations

Perforated and open-hole intervals.

FromToType
3,5643,570Perforated
3,8923,900Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62521212.25150 S
2.3753,560——
2.3753,900——
4.54,0157.875185 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
00Jul 8, 2010Apr 22, 2010—
00Dec 4, 2009Sep 18, 2009—
00Oct 28, 2009Jul 27, 2009—
00Jan 12, 1984Sep 23, 1982—
00Jan 12, 1984Jul 22, 1982—

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