WELL · 42-357-32482 · DISTRICT 10

Parnell 476 #3

N

Ochiltree County · Northrup (Cleveland) field  · Vertical

Parnell 476 #3 (API 42-357-32482) is a well in Ochiltree County operated by Latigo Petroleum Texas LP, completed February 6, 2005.

The RRC has issued one drilling permit, issued November 12, 2004, permitted to 7,700 ft.

Completion filings report one formation top, including Northrup (Cleveland).

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

Operator of record

Latigo Petroleum Texas LP

Houston, TX · P-5 Y, filed Sep 4, 2025 · 527 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLatigo Petroleum Texas LP
Production reportsUnbridled Resources, LLCthrough Jul 2022
Latest permitLatigo Petroleum Texas, LPNov 12, 2004

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

7,700
total depth, ft
1
permits on file
Nov 12, 2004
last permit issued
Feb 6, 2005
completed
0
cumulative oil, bbl
395K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2005 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 6, 2005
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
Parnell 476 G-14-208383Northrup (Cleveland)Unbridled Resources, LLC10395KFeb 2005 – Jul 2026
Parnell 476 O-14-7555Northrup (Cleveland)Latigo Petroleum Texas, LP100Feb 2005 – May 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. 1Latigo Petroleum Texas, LPFeb 2005 → Feb 2009
  2. 2Latigo Petroleum, Inc.Mar 2009 → Aug 2011
  3. 3Plains Exploration & Prod. Co.Sep 2011 → Mar 2012
  4. 4Linn Operating, Inc.Apr 2012 → Dec 2014
  5. 5Enervest Operating, L.L.C.Jan 2015 → Dec 2015
  6. 64P Energy Texas, LLCJan 2016 → Apr 2018
  7. 7Unbridled Resources, LLCJul 2022 → Jul 2022

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
553346-99DrillLatigo Petroleum Texas, LPNov 8, 2004Nov 12, 2004Dec 4, 20047,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-14-208383————
—— O-14-7555————

Formation tops

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

FormationMD ftSubsea
Northrup (Cleveland)7,300-4,472

Perforations

Perforated and open-hole intervals.

FromToType
7,3407,364Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,63011715 S
4.57,7007.875200 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
00Aug 4, 2005Apr 6, 2005—
00Jun 1, 2005Feb 14, 2005Yes
00May 25, 2005——
00Mar 22, 2005——

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