WELL · 42-023-31473 · DISTRICT 9

Fayette Co. School Land F #1

Plugged

Baylor County · Baylor County Regular field  · Vertical

Fayette CO. School Land F #1 (API 42-023-31473) is a plugged well in Baylor County, plugged June 24, 2013, last operated by Ryan Joseph G..

The RRC has issued one drilling permit, issued May 4, 1993, permitted to 6,000 ft.

It was permitted by Sunday Corporation and has since transferred to Ryan Joseph G. on the wellbore schedule.

Completion filings report 4 formation tops, including Palo Pinto, Caddo, Chester, Chappel.

Its lease has reported 7.64K barrels of oil and 28 mcf of gas since August 1993, last reporting in December 2013.

Operator of record

Ryan Joseph G.

Permitted by Sunday Corporation; the EWA schedule now lists a different operator.

Graham, TX · P-5 Y, filed Jul 4, 2026 · 10 permits on file · (940) 456-5235

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRyan Joseph G.
Production reportsMJM Oil & Gas, Inc.through Mar 1998
Latest permitSunday CorporationMay 4, 1993

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

6,000
total depth, ft
1
permits on file
May 4, 1993
last permit issued
Jul 9, 1993
completed
7.64K
cumulative oil, bbl
28
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 1993 THROUGH Dec 2013

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 9, 1993
Shut in
—
Plugged
Jun 24, 2013

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
Fayette Co. School Land "F" O-13-28620Baylor County RegularRyan, Joseph G.17.64K28Aug 1993 – Dec 2013

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. 1Sunday CorporationAug 1993 → Oct 1994
  2. 2Chardonnay Operating, Inc.Nov 1994 → Oct 1996
  3. 3Petroleum Capital, L.C.Nov 1996 → Feb 1998
  4. 4MJM Oil & Gas, Inc.Mar 1998 → Mar 1998

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
411371-99DrillSunday CorporationMay 4, 1993May 4, 1993May 18, 19936,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-28620————

Formation tops

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

FormationMD ftSubsea
Palo Pinto3,015-1,892
Caddo4,926-3,803
Chester5,363-4,240
Chappel5,372-4,249

Perforations

Perforated and open-hole intervals.

FromToType
4,9294,935Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62513512.25100 S
4.55,3807.875200 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
00Oct 15, 1993Aug 9, 1993Yes
00Aug 26, 1993——

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