WELL · 42-363-33610 · DISTRICT 7

Long C.B. #8

N

Palo Pinto County · C.B. Long (Ellenburger) field  · Vertical

Long C.B. #8 (API 42-363-33610) is a well in Palo Pinto County operated by Pittencrieff America Inc., completed September 8, 1985.

The RRC has issued 2 drilling permits between 1985 and 1992, permitted to 4,150 ft.

Completion filings report 2 formation tops, including Marble Falls, Dolomite-Limestone.

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

Operator of record

Pittencrieff America Inc.

Abilene, TX · P-5 Y, filed Aug 2, 2002 · 111 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePittencrieff America Inc.
Production reportsNordan Oil & Gas Corporationthrough Jul 2006
Latest permitPittencrieff America, Inc.Mar 17, 1992

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

4,150
total depth, ft
2
permits on file
Mar 17, 1992
last permit issued
Sep 8, 1985
completed
0
cumulative oil, bbl
188K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 8, 1985
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
Long, C.B. G-8-141089C.B. Long, (Marble Falls)Bluestem Resources LLC10188KJan 1993 – Jul 2026
Long, C.B. O-8-23116C.B. Long (Ellenburger)Pittencrieff America, Inc.100Jan 1993 – Dec 1993

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. 1Pittencrieff America, Inc.Jan 1993 → Apr 1998
  2. 2Nordan Oil & Gas CorporationMay 1998 → Jul 2006
  3. 3S. P. Penntex Energy, L.P.Jun 1998 → May 2003
  4. 4Penntex Resources, L.P.Jun 2003 → Sep 2005

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
397176-99RecompletionPittencrieff America, Inc.Mar 3, 1992Mar 17, 1992Jun 11, 19903,775
281053-99DrillDiscovery Exploration Corp.Aug 5, 1985Jul 25, 1985—4,150

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-141089————
—— O-8-23116————

Formation tops

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

FormationMD ftSubsea
Marble Falls3,314-2,338
Dolomite-Limestone3,820-2,844

Perforations

Perforated and open-hole intervals.

FromToType
3,3123,330Perforated
3,8083,810Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62521112.25130 S
5.53,8267.875350 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
00Jun 11, 1992Mar 2, 1992Yes
00Apr 14, 1992——
00Nov 14, 1985Oct 17, 1985Yes
00Nov 8, 1985——

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