WELL · 42-383-34254 · DISTRICT 7

Pink Cadillac #1

Plugged

Reagan County · Pink Panther (Siluro-Dev.) field  · Vertical

Pink Cadillac #1 (API 42-383-34254) is a plugged well in Reagan County, plugged March 23, 2005, last operated by Scythian Ltd..

The RRC has issued one drilling permit, issued December 3, 1993, permitted to 10,600 ft.

It was permitted by Collins & Ware, Inc. and has since transferred to Scythian Ltd. on the wellbore schedule.

Completion filings report 6 formation tops, including Dean, Wlf., Canyon, Strawn.

Its lease has reported 28.8K barrels of oil and 1.95K mcf of gas since January 1994, last reporting in April 2005.

Operator of record

Scythian Ltd.

Permitted by Collins & Ware, Inc.; the EWA schedule now lists a different operator.

Midland, TX · P-5 Y, filed Jul 4, 2026 · 7 permits on file · (432) 559-3870

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleScythian Ltd.
Production reportsNorthland Operating Companythrough May 1998
Latest permitCollins & Ware, Inc.Dec 3, 1993

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

10,600
total depth, ft
1
permits on file
Dec 3, 1993
last permit issued
Jan 21, 1994
completed
28.8K
cumulative oil, bbl
1.95K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1994 THROUGH Apr 2005

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 21, 1994
Shut in
—
Plugged
Mar 23, 2005

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
Pink Cadillac O-9-13585Pink Panther (Siluro-Dev.)Scythian, Ltd.128.8K1.95KJan 1994 – Apr 2005

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. 1Collins & Ware, Inc.Jan 1994 → Jul 1997
  2. 2Northland Operating CompanyAug 1997 → May 1998

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
418948-99DrillCollins & Ware, Inc.Dec 3, 1993Dec 3, 1993Dec 6, 199310,600

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-13585————

Formation tops

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

FormationMD ftSubsea
DeanDEAN SD.6,626-4,118
Wlf.6,786-4,278
CanyonCANYON SD8,441-5,933
Strawn9,176-6,668
Devonian9,476-6,968
Fusselman9,693-7,185

Perforations

Perforated and open-hole intervals.

FromToType
9,6549,668Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37556717.5550 S
9.6254,31412.25550 S
5.59,6708.7575 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
00Mar 30, 1994Feb 15, 1994Yes
00Mar 10, 1994——

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) and the University Lands library. 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/38334254, documented in the API reference.