WELL · 42-175-34115 · DISTRICT 2

Npu (O a Mudd 9A) #65

Y

Goliad County · Tulsita-Wilcox (MWC) field · Producing  · Vertical

Npu (O A Mudd 9a) #65 (API 42-175-34115) is a well in Goliad County operated by Paleo Oil Company LLC, completed March 16, 2009 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued September 12, 2008, permitted to 12,000 ft.

It was permitted by Legend Natural Gas II, LP and has since transferred to Paleo Oil Company LLC on the wellbore schedule.

Completion filings report one formation top, including Wilcox.

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

Operator of record

Paleo Oil Company LLC

Permitted by Legend Natural Gas II, LP; the EWA schedule now lists a different operator.

Based in
Corpus Christ, TX
P-5 status
Active (A)
P-5 last filed
Sep 10, 2025
Permits on file
47
Phone
(361) 904-0401

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePaleo Oil Company LLC
Production reportsTrinity River Energy Oper, LLCthrough Jan 2017
Latest permitLegend Natural Gas II, LPSep 12, 2008

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

12,000
total depth, ft
1
permits on file
Sep 12, 2008
last permit issued
Mar 16, 2009
completed
0
cumulative oil, bbl
12.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 16, 2009
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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
Npu (O a Mudd 9A) G-2-253952Tulsita-Wilcox (MWC)Paleo Oil Company LLC1012.1KMar 2009 – 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. 1Legend Natural Gas II, LPMar 2009 → Nov 2011
  2. 2Trinity River Energy Oper, LLCJan 2017 → Jan 2017

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
669809-99DrillLegend Natural Gas II, LPAug 25, 2008Sep 12, 2008Jan 28, 200912,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-253952————

Formation tops

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

FormationMD ftSubsea
Wilcox6,851-6,464

Perforations

Perforated and open-hole intervals.

FromToType
8,9798,986Perforated
9,0529,058Perforated
9,0879,089Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.59276.125160 S
9.6251,19212.25530 S
77,4308.75154 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
00Mar 11, 2010Sep 28, 2009Yes
00Jan 8, 2010——

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