WELL · 42-227-34737 · DISTRICT 8

Roadrunner #1

Plugged

Howard County · Double B (Canyon) field  · Vertical

Roadrunner #1 (API 42-227-34737) is a plugged well in Howard County, plugged July 13, 2017, last operated by Lakewood Operating Ltd..

The RRC has issued one drilling permit (amended once), issued December 22, 1992, permitted to 7,800 ft.

Completion filings report 4 formation tops, including Clear Fork, Wolfcamp, Pennsylvanian, Canyon.

Its 2 leases have reported 372K barrels of oil and 610K mcf of gas since March 1993, last reporting in March 2018. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Lakewood Operating Ltd.

Based in
Midland, TX
P-5 status
Active (A)
P-5 last filed
Feb 5, 2026
Permits on file
110
Phone
(432) 683-6391

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLakewood Operating Ltd.
Production reportsLakewood Operating, Ltd.through Feb 2017
Latest permitLakewood Operating, Ltd.Dec 22, 1992
7,800
total depth, ft
2
permits on file
Dec 22, 1992
last permit issued
Feb 8, 1993
completed
372K
cumulative oil, bbl
610K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 1993 THROUGH Mar 2018

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 8, 1993
Shut in
—
Plugged
Jul 13, 2017

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Roadrunner O-10-33879Double "B" (Canyon)Lakewood Operating, Ltd.1372K585KApr 1993 – Mar 2018
Roadrunner G-10-144593Double "B" (Canyon)Lakewood Operating, Ltd.1024.9KMar 1993 – Aug 1993

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. 1Lakewood Operating, Ltd.Mar 1993 → Sep 2015

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
407414-98DrillLakewood Operating, Ltd.Feb 8, 1993Dec 22, 1992—7,800
407414-99DrillLakewood Operating, Ltd.Dec 18, 1992Dec 22, 1992Jan 4, 19937,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-10-144593————
—— O-10-33879————

Formation tops

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

FormationMD ftSubsea
Clear ForkUPPER CLEARFORK3,785-1,418
Clear ForkLOWER CLEARFORK4,430-2,063
Wolfcamp5,566-3,199
PennsylvanianPENN6,198-3,831
CanyonCANYON LIME7,266-4,899

Perforations

Perforated and open-hole intervals.

FromToType
7,3137,345Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37540417.5400 S
8.6252,346111,000 S
5.57,3137.8751,040 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 18, 1993Jun 18, 1993—
00Jul 27, 1993——
00May 17, 1993Mar 19, 1993Yes
00Apr 6, 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/22734737, documented in the API reference.