WELL · 42-485-46066 · DISTRICT 9

Lockridge #10

Plugged

Wichita County · Wichita County Regular field  · Vertical

Lockridge #10 (API 42-485-46066) is a plugged well in Wichita County, plugged November 30, 2017, last operated by G D Energy Corporation.

The RRC has issued one drilling permit, issued November 20, 2017, permitted to 1,999 ft.

It was permitted by G D Energy Corporation and has since transferred to G D Energy Corporation on the wellbore schedule.

Operator of record

G D Energy Corporation

Permitted by G D Energy Corporation; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitG D Energy CorporationNov 20, 2017

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

1,999
total depth, ft
1
permits on file
Nov 20, 2017
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
Nov 30, 2017

Surface location

33.879207, -98.706599

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Wichita 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
832851-99DrillG D Energy CorporationNov 6, 2017Nov 20, 2017Nov 27, 20171,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 8 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 →

Lochridge Unit42-485-46111

1.5 KM · Gilmore, Leo Oil, Inc. · Section with this well →

Cisco886118
Thomas Sand1,670-666
Gunsight1,772-768
Gunsight1,800-796
Canyon2,048-1,044
KMA—
Vogstberger—
Tannehill—

10 TOPS · FIRST 8

Cbld42-485-46121

1.8 KM · JDL Operating, LLC · Section with this well →

Gunsight1,960
Gunsight2,030
Canyon2,300
Bluff Creek Sand2,880
Strawn3,400
KMA3,940
Cisco—
Thomas Sand—

10 TOPS · FIRST 8

Chilson42-485-46112

2.0 KM · Cholla Petroleum, Inc. · Section with this well →

Gunsight1,960-955
Gunsight2,030-1,025
Canyon2,300-1,295
Bluff Creek Sand2,880-1,875
Strawn3,400-2,395
KMA3,940-2,935
Tannehill—
Vogstberger—

10 TOPS · FIRST 8

Kempner Unit42-485-45948

2.1 KM · White Knight Production LLC · Section with this well →

Gunsight1,730
Gunsight1,755
Canyon2,001
KMA3,700
Kma Lime3,796
Bluff Creek Sand—
Cisco—
Strawn—

11 TOPS · FIRST 8

Bishop -A-42-485-46292

2.3 KM · S&G Oil LLC · Section with this well →

Tannehill496
Cisco812
Thomas Sand1,120
Gunsight1,768
Gunsight1,782
Bluff Creek Sand—
Vogstberger—
Strawn—

10 TOPS · FIRST 8

JT Cole42-485-46130

2.8 KM · True Wolf Operating, LLC · Section with this well →

Thomas Sand1,510
Bluff Creek Sand—
Canyon—
Cisco—
Gunsight—
Gunsight—
KMA—
Strawn—

10 TOPS · FIRST 8

Scott42-485-46052

3.1 KM · Abb Oil Co., Inc. · Section with this well →

Gunsight1,907
Gunsight—
KMA—
Strawn—
Bluff Creek Sand—
Thomas Sand—
Cisco—
Tannehill—

10 TOPS · FIRST 8

JT Cole42-485-46129

3.4 KM · True Wolf Operating, LLC · Section with this well →

Cisco200
Tannehill300
Vogstberger—
Canyon—
Bluff Creek Sand—
Gunsight—
Gunsight—
KMA—

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