WELL · 42-317-35621 · DISTRICT 8

Dorothy Faye -A319- #3

N

Martin County  · Vertical

Dorothy Faye -A319- #3 (API 42-317-35621) is a permitted well in Martin County filed by H & M Resources, LLC; no completion report is on file yet.

The RRC has issued one drilling permit (amended once), issued June 10, 2009, permitted to 12,539 ft.

Completion filings report 4 formation tops, including Spraberry, Dean, Wolfcamp, Pennsylvanian.

Its lease has reported 506K barrels of oil and 2.19M mcf of gas since June 2009, last reporting in July 2026. The lease carries 8 wells, so these are lease totals, not this well alone.

Operator of record

H & M Resources, LLC

Dallas, TX · P-5 Y, filed Feb 4, 2026 · 63 permits on file · (214) 538-7366

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsOvintiv USA Inc.through Apr 2026
Latest permitH & M Resources, LLCJun 10, 2009
12,539
total depth, ft
2
permits on file
Jun 10, 2009
last permit issued
—
completed
506K
cumulative oil, bbl
2.19M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
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 lease this well is completed on; they carry 8 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Dorothy Faye -A319- O-10-39632Spraberry (Trend Area)Ovintiv USA Inc.8506K2.19MJun 2009 – Jul 2026

Gas, mcf lease total

Last 12 months 73,297 · prior 12 121,086(-39%)

05K10K15K202420252026

Oil, barrels lease total

Last 12 months 5,478 · prior 12 9,922(-45%)

01K2K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1H & M Resources, LLCJun 2009 → Apr 2013
  2. 2Hibernia Resources, LLCMay 2013 → May 2014
  3. 3Athlon Holdings LPJun 2014 → Jan 2015
  4. 4Encana Oil & Gas(usa) Inc.Feb 2015 → Jan 2020
  5. 5Ovintiv USA Inc.Feb 2020 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
681977-98DrillH & M Resources, LLCMay 14, 2013Jun 10, 2009Jun 18, 200912,539
681977-99DrillH & M Resources, LLCJun 9, 2009Jun 10, 2009Jun 18, 200912,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-39632————

Formation tops

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

FormationMD ftSubsea
Spraberry8,275-5,363
Dean9,466-6,554
Wolfcamp9,980-7,068
PennsylvanianPENN10,529-7,617

Perforations

Perforated and open-hole intervals.

FromToType
8,58010,530Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37541517.5450 S
8.6255,33411900 S
5.512,1547.8751,250 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 22, 2013Dec 29, 2011Yes

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