WELL · 42-183-30710 · DISTRICT 6

Killingsworth B #2

Plugged

Gregg County · Willow Springs W.(tr. Pk.) field  · Directional

Killingsworth B #2 (API 42-183-30710) is a plugged well in Gregg County, plugged December 7, 2011, last operated by Eog Resources Inc..

The RRC has issued one drilling permit, issued July 29, 1987, permitted to 8,100 ft.

It was permitted by Cities Service Oil & Gas Corp. and has since transferred to Eog Resources Inc. on the wellbore schedule.

Completion filings report 5 formation tops, including Austin Chalk, Travis Peak, Upper Killingsworth, Lower Killingsworth.

Operator of record

EOG Resources Inc.

Permitted by Cities Service Oil & Gas Corp.; the EWA schedule now lists a different operator.

Midland, TX · P-5 Y, filed Jul 4, 2026 · 16,348 permits on file · (713) 594-5431

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEOG Resources Inc.
Production reportsEOG Resources, Inc.through Jun 2001
Latest permitCities Service Oil & Gas Corp.Jul 29, 1987

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

8,100
total depth, ft
1
permits on file
Jul 29, 1987
last permit issued
Nov 3, 1987
completed
0
cumulative oil, bbl
438
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Dec 2011

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Nov 3, 1987
Shut in
—
Plugged
Dec 7, 2011

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
Killingsworth "B" G-6-125783Willow Springs, W.(tr. Pk.)EOG Resources, Inc.10438Jan 1993 – Dec 2011

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. 1OXY USA Inc.Sep 1999 → Dec 1999
  2. 2EOG Resources, Inc.Feb 2000 → Jun 2001

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
333710-99DrillCities Service Oil & Gas Corp.Jul 29, 1987Jul 29, 1987—8,100

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-125783————

Formation tops

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

FormationMD ftSubsea
Austin ChalkBASE AUSTIN CHALK3,003-2,573
Travis Peak8,405-7,975
Upper Killingsworth8,440-8,010
Lower Killingsworth8,475-8,045
Lower Killingsworth SS8,475-8,045

Perforations

Perforated and open-hole intervals.

FromToType
8,4538,530Perforated
8,5308,534Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6253,70012.25595 S
5.58,6608.75715 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
00Mar 14, 1995Jan 5, 1995—
00Mar 11, 1988Feb 8, 1988—
00Jan 13, 1988Nov 23, 1987Yes
00Jan 8, 1988——

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