WELL · 42-367-33427 · DISTRICT 7

Phoenix Family Group #1

N

Parker County · Wildcat field  · Vertical

Phoenix Family Group #1 (API 42-367-33427) is a well in Parker County operated by P-R-O Management Inc., completed September 27, 2002.

The RRC has issued 2 drilling permits (amended once) between 2002 and 2005, permitted to 5,800 ft.

Completion filings report 6 formation tops, including Parks Lm, Parks Ls, Caddo, Atoka.

No lease production has been reported under this well’s leases.

Operator of record

P-R-O Management Inc.

Dallas, TX · P-5 Y, filed May 4, 2012 · 34 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleP-R-O Management Inc.
Production reportsShell Western E&Pthrough Aug 2006
Latest permitP-R-O Management, Inc.Jan 20, 2005

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

5,800
total depth, ft
3
permits on file
Jan 20, 2005
last permit issued
Sep 27, 2002
completed
0
cumulative oil, bbl
2.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2002 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 27, 2002
Shut in
—
Plugged
—

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Phoenix Family Group G-8-205799Buckner(strawn)Anre Gas Systems, Inc.102.4KAug 2004 – Jul 2026
Phoenix Family Group G-8-192581WildcatP-R-O Management, Inc.100Sep 2002 – Aug 2004

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. 1P-R-O Management, Inc.Dec 2004 → Dec 2005
  2. 2Shell Western E&PMay 2006 → Aug 2006

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
556504-99Field transferP-R-O Management, Inc.Jan 20, 2005Jan 20, 2005—5,374
522431-98DrillP-R-O Management, Inc.Aug 2, 2002Aug 1, 2002Aug 20, 20025,800
522431-99DrillP-R-O Management, Inc.Aug 1, 2002Aug 1, 2002—5,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-192581————
—— G-8-205799————

Formation tops

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

FormationMD ftSubsea
Parks LM81472
Parks LS81472
CaddoCADDO LM1,252-366
CaddoCADDO LS1,252-366
Atoka1,670-784
AtokaATOKA SD.1,670-784
Marble Falls4,940-4,054
Barnett5,210-4,324

Perforations

Perforated and open-hole intervals.

FromToType
1,6741,680Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62550412.25320 S
4.51,9807.875325 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
00Apr 18, 2005Aug 23, 2001—
00Feb 1, 2005——
00Mar 7, 2003Dec 6, 2002Yes
00Feb 5, 2003——

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