WELL · 42-155-30809 · DISTRICT 9

L.K. Johnson #6N

Plugged

Foard County · Wildcat field  · Vertical

L.K. Johnson #6N (API 42-155-30809) is a plugged well in Foard County, plugged March 9, 2019, last operated by Nwg Operating LLC.

The RRC has issued one drilling permit, issued February 4, 2019, permitted to 6,999 ft.

It was permitted by Nwg Operating LLC and has since transferred to Nwg Operating LLC on the wellbore schedule.

Operator of record

NWG Operating LLC

Permitted by NWG Operating LLC; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitNWG Operating LLCFeb 4, 2019

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

6,999
total depth, ft
1
permits on file
Feb 4, 2019
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Mar 9, 2019

Surface location

33.969105, -100.037235

OpenStreetMap → ·  Google Maps →

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

Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
849559-99DrillNWG Operating LLCFeb 4, 2019Feb 4, 2019Feb 22, 20196,999

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 5 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well has no tops filed, so it cannot anchor a section; its neighbours can.

Section of the neighbours →

LK Johnson42-155-30810

1.0 KM · NWG Operating LLC · Section with this well →

Coleman Junction1,924-315
Gunsite3,233-1,624
Canyon3,564-1,955
Palo Pinto—
Raspberry—
Strawn—
Bend—
Caddo—

10 TOPS · FIRST 8

L.K. Johnson42-155-30808

1.0 KM · NWG Operating LLC · Section with this well →

Coleman Junction1,920-296
Tannehill2,440-816
Gunsite3,234-1,610
Cisco3,500-1,876
Canyon3,536-1,912
Raspberry—
Strawn—
Caddo—

10 TOPS · FIRST 8

L.K. Johnson42-101-30755

1.1 KM · NWG Operating LLC · Section with this well →

Gunsight3,300-1,636
Bend—
Caddo—
Canyon—
Cisco—
Coleman Junction—
Palo Pinto—
Rasperry—

10 TOPS · FIRST 8

Johnson, L. K.42-155-30815

1.9 KM · NWG Operating LLC · Section with this well →

Coleman Junction1,967-347
Tannehill2,457-837
Gunsite3,325-1,705
Cisco3,629-2,009
Canyon3,730-2,110
Raspberry—
Strawn—
Caddo—

10 TOPS · FIRST 8

Rasberry /6100 Caddo/ Unit42-155-00152

15.1 KM · Falcon Production LLC · Section with this well →

Caddo6,112-4,331

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