WELL · 42-337-32603 · DISTRICT 9

JCS #1

Plugged

Montague County · Montague County Regular field  · Vertical

Jcs #1 (API 42-337-32603) is a plugged well in Montague County, plugged August 18, 2003, last operated by Pruitt Oil & Gas.

The RRC has issued 2 drilling permits between 1985 and 1990, permitted to 7,500 ft.

It was permitted by Mayco Oil and has since transferred to Pruitt Oil & Gas on the wellbore schedule.

Completion filings report 3 formation tops, including Bryson, Caddo, Ellenburger.

Its 2 leases have reported 8.11K barrels of oil and 75 mcf of gas since January 1993, last reporting in October 2003.

Operator of record

Pruitt Oil & Gas

Permitted by Mayco Oil; the EWA schedule now lists a different operator.

Decatur, TX · P-5 Y, filed Mar 2, 2018 · 9 permits on file · (940) 704-1680

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePruitt Oil & Gas
Production reportsPruitt Oil & Gasthrough Jul 2003
Latest permitMayco OilAug 29, 1990

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

7,500
total depth, ft
2
permits on file
Aug 29, 1990
last permit issued
Aug 14, 1990
completed
8.11K
cumulative oil, bbl
75
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Oct 2003

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 14, 1990
Shut in
—
Plugged
Aug 18, 2003

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
JCS O-13-27934Montague County RegularPruitt Oil & Gas18.11K75Jan 1993 – Oct 2003
— O-13-25987——000—

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. 1Mayco OilJan 1993 → Aug 1999
  2. 2Pruitt Oil & GasOct 1999 → Jul 2003

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
376852-99RecompletionMayco OilAug 27, 1990Aug 29, 1990—4,980
289113-99DrillMayco OilOct 28, 1985Oct 29, 1985—7,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-25987————
—— O-13-27934————

Formation tops

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

FormationMD ftSubsea
Bryson4,889-3,978
BrysonBRYSON LIME4,892-3,981
CaddoCADDO LIME5,844-4,933
EllenburgerELLENBERGER6,652-5,741

Perforations

Perforated and open-hole intervals.

FromToType
4,9204,924Perforated
5,9725,982Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62595712.25500 S
4.54,980—100 S
4.56,9507.875270 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
00Apr 8, 1991Aug 22, 1990Yes
00Mar 7, 1991Feb 12, 1986Yes
00Mar 6, 1986Feb 12, 1986Yes
00Mar 1, 1986——

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