WELL · 42-417-34537 · DISTRICT 7

Nail 135 (M-J) #6A

Y

Shackelford County · Roark-Nail field · NO Production  · Vertical

Nail 135 (M-J) #6A (API 42-417-34537) is a well in Shackelford County operated by Clavo Oil LLC, completed April 22, 1982 and listed as no production on the RRC schedule.

The RRC has issued one drilling permit, issued April 27, 1982, permitted to 1,900 ft.

It was permitted by Musselman Petroleum & Land CO. and has since transferred to Clavo Oil LLC on the wellbore schedule.

Its lease has reported 156K barrels of oil and 81 mcf of gas since January 1993, last reporting in July 2026. The lease carries 15 wells, so these are lease totals, not this well alone.

Operator of record

Clavo Oil LLC

Permitted by Musselman Petroleum & Land Co.; the EWA schedule now lists a different operator.

Graham, TX · P-5 Y, filed Dec 4, 2025 · 61 permits on file · (325) 725-5575

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleClavo Oil LLC
Production reportsFTC Consulting, LLCthrough Jul 2024
Latest permitMusselman Petroleum & Land Co.Apr 27, 1982

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

1,900
total depth, ft
1
permits on file
Apr 27, 1982
last permit issued
Apr 22, 1982
completed
156K
cumulative oil, bbl
81
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 22, 1982
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Nail 135 (M-J) O-8-17362Roark-NailClavo Oil, LLC15156K81Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 0 · prior 12 6(-100%)

0102030202420252026

Chain of custody

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

  1. 1Jones Company, Ltd.Jan 1993 → Mar 1996
  2. 2Frontier Operating CorporationApr 1996 → Jul 1997
  3. 3Edington Oil CompanyAug 1997 → Jul 2002
  4. 4Stasney, H. R. & Sons, Ltd.Aug 2002 → Mar 2009
  5. 5Stasney Well Service, LLCApr 2009 → Jul 2021
  6. 6FTC Consulting, LLCAug 2021 → Jul 2024

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
158376-99DrillMusselman Petroleum & Land Co.Apr 27, 1982Apr 27, 1982—1,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-17362————

Perforations

Perforated and open-hole intervals.

FromToType
1,4931,502Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251011080 S
2.3751,521——
4.51,7007.875100 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
00Jan 12, 1984May 11, 1982—

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