WELL · 42-135-35067 · DISTRICT 8

Johnson -B-43- #1

Plugged

Ector County · Cowden North (Canyon) field  · Vertical

Johnson -B-43- #1 (API 42-135-35067) is a plugged well in Ector County, plugged July 2, 2024, last operated by Slant Operating LLC.

The RRC has issued one drilling permit, issued September 5, 1985, permitted to 9,700 ft.

It was permitted by Arco Oil & Gas CO. and has since transferred to Slant Operating LLC on the wellbore schedule.

Completion filings report 7 formation tops, including Rustler, Yates, Grayburg, San Andres.

Its lease has reported 3.47K barrels of oil and 7.51K mcf of gas since January 1993, last reporting in September 2024.

Operator of record

Slant Operating LLC

Permitted by Arco Oil & Gas Co.; the EWA schedule now lists a different operator.

Lafayette, LA · P-5 Y, filed Oct 4, 2025 · 194 permits on file · (337) 534-0135

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSlant Operating LLC
Production reportsArco Permianthrough Jun 1998
Latest permitArco Oil & Gas Co.Sep 5, 1985

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

9,700
total depth, ft
1
permits on file
Sep 5, 1985
last permit issued
Jun 16, 1998
completed
3.47K
cumulative oil, bbl
7.51K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Sep 2024

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 16, 1998
Shut in
—
Plugged
Jul 2, 2024

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
Johnson -B-43- O-10-30273Cowden, North (Canyon)Slant Operating, LLC13.47K7.51KJan 1993 – Sep 2024

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. 1Arco Oil & Gas Co.Jan 1993 → May 1994
  2. 2Arco PermianJun 1994 → Jun 1998

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
284107-99DrillArco Oil & Gas Co.Sep 5, 1985Sep 5, 1985—9,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-30273————

Formation tops

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

FormationMD ftSubsea
Rustler1,7501,226
Yates2,88690
Grayburg4,063-1,087
San Andres4,492-1,516
Holt5,330-2,354
GlorietaGLORIETTA5,415-2,439
Canyon8,848-5,872

Perforations

Perforated and open-hole intervals.

FromToType
8,8519,136Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37531417.5350 S
115,00511150 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
00Aug 12, 1998Jul 16, 1998—
00Dec 18, 1985Nov 6, 1985Yes
00Dec 7, 1985——

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) and the University Lands library. 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/13535067, documented in the API reference.