WELL · 42-077-35063 · DISTRICT 9

Mayo J.H. -A- #23

Y

Clay County · Clay County Regular field · Producing  · Vertical

Mayo J.H. -A- #23 (API 42-077-35063) is a well in Clay County operated by Mountain Creek Oil Company Inc., completed March 1, 2009 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued January 28, 2009, permitted to 1,000 ft.

It was permitted by IT'LL DO Oil Company and has since transferred to Mountain Creek Oil Company Inc. on the wellbore schedule.

Completion filings report one formation top, including Cisco.

Its lease has reported 30.1K barrels of oil and 42 mcf of gas since April 2001, last reporting in July 2026. The lease carries 9 wells, so these are lease totals, not this well alone.

Operator of record

Mountain Creek Oil Company Inc.

Permitted by It'll DO Oil Company; the EWA schedule now lists a different operator.

Saint JO, TX · P-5 Y, filed Jul 4, 2026 · 68 permits on file · (940) 872-7314

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMountain Creek Oil Company Inc.
Production reportsMountain Creek Oil Company, Inc.through Apr 2026
Latest permitIt'll DO Oil CompanyJan 28, 2009

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

1,000
total depth, ft
1
permits on file
Jan 28, 2009
last permit issued
Mar 1, 2009
completed
30.1K
cumulative oil, bbl
42
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2001 THROUGH Jul 2026

Regulatory status · RRC wellbore file

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

Operator's P-5 on the schedule: Active

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 9 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Mayo, J.H. -A- O-13-29868Clay County RegularMountain Creek Oil Company, Inc.930.1K42Apr 2001 – Jul 2026

Oil, barrels lease total

Last 12 months 693 · prior 12 763(-9%)

050100150202420252026

Chain of custody

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

  1. 1It'll DO Oil CompanyJul 2001 → Nov 2024
  2. 2Mountain Creek Oil Company, Inc.Dec 2024 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
672219-99DrillIt'll DO Oil CompanySep 30, 2008Jan 28, 2009Feb 6, 20091,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-29868————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
Cisco732

Perforations

Perforated and open-hole intervals.

FromToType
798804Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.59707.875225 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 13, 2009May 19, 2009Yes
00Sep 25, 2009——

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