WELL · 42-077-35404 · DISTRICT 9

Klement #1

Y

Clay County · Keeton (Bennett Sand) field · Producing  · Vertical

Klement #1 (API 42-077-35404) is a well in Clay County operated by Muirfield Exploration Ltd., completed August 1, 2025 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued June 13, 2025, permitted to 2,000 ft.

Completion filings report 10 formation tops, including Cisco, Keeton (Bennett Sand), Canyon, Granite Wash.

Its lease has reported 5.88K barrels of oil since July 2025, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Muirfield Exploration Ltd.

Wichita Falls, TX · P-5 Y, filed Jun 4, 2026 · 199 permits on file · (405) 464-9846

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMuirfield Exploration Ltd.
Production reportsMuirfield Exploration, Ltd.through Mar 2026
Latest permitMuirfield Exploration, Ltd.Jun 13, 2025
2,000
total depth, ft
1
permits on file
Jun 13, 2025
last permit issued
Aug 1, 2025
completed
5.88K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2025 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 1, 2025
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

34.011199, -98.186282

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Clay County.

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
Klement O-13-34396Keeton (Bennett Sand)Muirfield Exploration, Ltd.25.88K0Jul 2025 – Jul 2026

Oil, barrels lease total

Last 12 months 5,876 · prior 12 0

05001K202420252026

Chain of custody

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

  1. 1Muirfield Exploration, Ltd.Jul 2025 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
908563-99DrillMuirfield Exploration, Ltd.Jun 11, 2025Jun 13, 2025Jun 16, 20252,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-34396————

Formation tops

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

FormationMD ftSubsea
CiscoCISCO SERIES1,810-827
Keeton (Bennett Sand)1,819-836
Canyon1,972-989
Granite Wash——
GunsightGUNSIGHT SAND——
Overcharged Disposal Zone - 4 MI——
StrawnSTRAWN SAND——
Thomas Sand——
Undetermined - Gas Producing Zon——
Weir——

Perforations

Perforated and open-hole intervals.

FromToType
1,8191,823Perforated
1,8781,882Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62521112.25150 S
4.51,9846.75275 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 9, 2025Sep 17, 2025—
00Aug 4, 2025Jul 30, 2025Yes

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Keeton42-077-35400

0.1 KM · Muirfield Exploration, Ltd. · Section with this well →

Cisco1,795-811
Keeton (Bennett Sand)1,804-820
Canyon1,958-974
Thomas Sand—
Strawn—
Overcharged Disposal Zone - 4 MI—
Gunsight—
Granite Wash—

10 TOPS · FIRST 8

Klement42-077-35406

0.1 KM · Muirfield Exploration, Ltd. · Section with this well →

Cisco1,818-842
Keeton (Bennett Sand)1,835-859
Canyon1,986-1,010
Thomas Sand—
Strawn—
Overcharged Disposal Zone - 4 MI—
Undetermined - Gas Producing Zon—
Gunsight—

10 TOPS · FIRST 8

Keeton42-077-35407

0.1 KM · Muirfield Exploration, Ltd. · Section with this well →

Cisco1,800-815
Keeton (Bennett Sand)1,808-823
Canyon1,974-989
Weir—
Strawn—
Overcharged Disposal Zone - 4 MI—
Gunsight—
Granite Wash—

10 TOPS · FIRST 8

Keeton42-077-35331

0.1 KM · Muirfield Exploration, Ltd. · Section with this well →

Canyon—
Cisco—
Granite Wash—
Gunsight—
Mobley Sand—
Overcharged Disposal Zone - 4 MI—
Strawn—
Thomas Sand—

10 TOPS · FIRST 8

Keeton42-077-35316

0.2 KM · Muirfield Exploration, Ltd. · Section with this well →

Cisco1,768-791
Bennett Sand1,776-799
Canyon1,942-965
Overcharged Disposal Zone - 4 MI—
Strawn—
Thomas Sand—
Undetermined - Gas Producing Zon—
Gunsight—

10 TOPS · FIRST 8

Keeton42-077-35341

0.2 KM · Muirfield Exploration, Ltd. · Section with this well →

Cisco1,768-791
Bennett Sand1,782-805
Canyon—
Granite Wash—
Gunsight—
Overcharged Disposal Zone - 4 MI—
Strawn—
Thomas Sand—

10 TOPS · FIRST 8

Keeton42-077-35322

0.2 KM · Muirfield Exploration, Ltd. · Section with this well →

Canyon1,911-931
Undetermined - Gas Producing Zon—
Thomas Sand—
Strawn—
Overcharged Disposal Zone - 4 MI—
Mobley Sand—
Gunsight—
Granite Wash—

10 TOPS · FIRST 8

Keeton42-077-35321

0.2 KM · Muirfield Exploration, Ltd. · Section with this well →

Cisco1,751-771
Bennett Sand1,760-780
Canyon1,920-940
Granite Wash—
Gunsight—
Overcharged Disposal Zone - 4 MI—
Strawn—
Thomas Sand—

10 TOPS · FIRST 8

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