WELL · 42-353-31479 · DISTRICT 7

Parsons #1

N

Nolan County · Parsons (Strawn Sand) field  · Vertical

Parsons #1 (API 42-353-31479) is a well in Nolan County operated by Hudson Resources, completed September 2, 1983.

The RRC has issued 2 drilling permits between 1983 and 1984, permitted to 6,700 ft.

Completion filings report 4 formation tops, including Cisco, Canyon, Strawn, Ellenburger.

Its lease has reported 130K barrels of oil and 144K mcf of gas since January 1993, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Hudson Resources

Dallas, TX · P-5 Y, filed Feb 15, 1991 · 13 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHudson Resources
Production reportsClear Fork, Incorporatedthrough Apr 2026
Latest permitHudson ResourcesSep 14, 1984

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

6,700
total depth, ft
2
permits on file
Sep 14, 1984
last permit issued
Sep 2, 1983
completed
130K
cumulative oil, bbl
144K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 2, 1983
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 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Parsons O-8-21021Parsons (Ellenburger)Clear Fork, Incorporated2130K144KJan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 3,033 · prior 12 3,896(-22%)

0200400600202420252026

Gas, mcf lease total

Last 12 months 2,515 · prior 12 2,981(-16%)

0200400202420252026

Chain of custody

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

  1. 1Munn, W. H. Operating CompanyJan 1993 → May 2002
  2. 2Clear Fork, IncorporatedJun 2002 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
251382-99RecompletionHudson ResourcesSep 12, 1984Sep 14, 1984—6,625
201232-99DrillHudson ResourcesJul 12, 1983Jul 12, 1983Jul 13, 19836,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-21021————

Formation tops

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

FormationMD ftSubsea
Cisco4,030-1,774
CanyonCANYON REEF5,120-2,864
StrawnSTRAWN SAND5,561-3,305
Ellenburger6,510-4,254

Perforations

Perforated and open-hole intervals.

FromToType
5,5615,566Perforated
6,5646,578Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62581512.25450 S
2.3755,660——
5.56,6257.8751,000 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
00Jan 4, 1985Sep 21, 1984—
00Dec 11, 1984——
00Jan 12, 1984Sep 23, 1983—

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