WELL · 42-109-32476 · DISTRICT 8

Harrier 14 #1

Y

Culberson County · Ford West (4100) field · Shut IN  · Vertical

Harrier 14 #1 (API 42-109-32476) is a well in Culberson County operated by Echo Energy Partners LLC, completed October 4, 2012 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued June 5, 2012, permitted to 5,500 ft.

It was permitted by Finley Resources, Inc. and has since transferred to Echo Energy Partners LLC on the wellbore schedule.

Completion filings report 4 formation tops, including Lamar, Ramsey, Olds, Cherry Canyon.

Its lease has reported 224 barrels of oil since October 2012, last reporting in July 2026.

Operator of record

Echo Energy Partners LLC

Permitted by Finley Resources, Inc.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Feb 2, 2026 · (844) 443-2371

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEcho Energy Partners LLC
Production reportsFinley Resources, Inc.through Apr 2014
Latest permitFinley Resources, Inc.Jun 5, 2012

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

5,500
total depth, ft
1
permits on file
Jun 5, 2012
last permit issued
Oct 4, 2012
completed
224
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2012 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 4, 2012
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Harrier 14 O-10-44022Ford, West (4100)Echo Energy Partners, LLC12240Oct 2012 – Jul 2026

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. 1Finley Resources, Inc.Mar 2013 → Apr 2014

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
740405-99DrillFinley Resources, Inc.May 10, 2012Jun 5, 2012Jul 25, 20125,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-44022————

Formation tops

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

FormationMD ftSubsea
Lamar2,516563
Ramsey2,554525
Olds2,584495
Cherry Canyon3,474-395

Perforations

Perforated and open-hole intervals.

FromToType
3,9684,028Perforated
4,1354,360Perforated
4,5304,710Perforated
5,1365,468Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37545317.5375 S
8.6252,384111,150 S
5.55,5337.875375 S
5.5—7.875650 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
00May 12, 2014May 8, 2013Yes

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