WELL · 42-269-33048 · DISTRICT 8

Bacon C #1C

Plugged

King County · Bee Wright Tannehill) field  · Vertical

Bacon C #1C (API 42-269-33048) is a plugged well in King County, plugged November 19, 2024, last operated by Salida Exploration LLC.

The RRC has issued one drilling permit, issued November 1, 2024, permitted to 4,000 ft.

It was permitted by Salida Exploration, LLC and has since transferred to Salida Exploration LLC on the wellbore schedule.

Operator of record

Salida Exploration LLC

Permitted by Salida Exploration, LLC; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitSalida Exploration, LLCNov 1, 2024

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

4,000
total depth, ft
1
permits on file
Nov 1, 2024
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 19, 2024

Surface location

33.452100, -100.291200

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in King 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
903671-99DrillSalida Exploration, LLCOct 30, 2024Nov 1, 2024Nov 12, 20244,000

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 7 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 →

Crum42-269-33008

3.3 KM · Salida Exploration, LLC · Section with this well →

Coleman Junction2,665-928
Tannehill3,233-1,496
Caddo—
Conglomerate—
Cisco—
Canyon—
Bunger—
Strawn—

10 TOPS · FIRST 8

Sixes Pick42-269-33063

4.2 KM · Gunn Oil Company · Section with this well →

Coleman Junction2,702-900
Tannehill3,254-1,452
Cisco4,180-2,378
Canyon4,363-2,561
Pennsylvanian4,567-2,765
Des Moines5,421-3,619
Strawn5,421-3,619
Bunger—

10 TOPS · FIRST 8

Simpson42-269-33064

5.6 KM · Salida Exploration, LLC · Section with this well →

Stockwether Lime3,320-1,545
Tannehill3,392-1,617
Coleman Junction—
Canyon—
Cisco—
Conglomerate—
Des Moines—
Bunger—

10 TOPS · FIRST 8

Four Sixes 'A'42-269-32985

10.6 KM · Burnett Oil Co., Inc. · Section with this well →

Coleman Junction2,712-902
Dothan Base3,096-1,286
Cisco4,070-2,260
Bunger4,319-2,509
Canyon5,162-3,352
Strawn5,222-3,412
Conglomerate—
Des Moines—

10 TOPS · FIRST 8

Bissett '60'42-433-33610

13.7 KM · Vertox LLC · Section with this well →

Tannehill3,168-1,386
Strawn5,529-3,747
Bend6,062-4,280
Crystal Falls - Disposal—
Dothan Lime - Disposal—
Flippen - Disposal—
Home Creek - Disposal—
Cisco—

11 TOPS · FIRST 8

Springer 'A'42-269-33014

14.1 KM · Sojourner Drilling Corporation · Section with this well →

Coleman Junction3,215-1,283
Tannehill3,708-1,776
Strawn5,589-3,657

Springer '196'42-269-32977

15.5 KM · TDC Engineering, Inc. · Section with this well →

Bunger—
Tannehill—
Strawn—
Pennsylvanian—
Des Moines—
Conglomerate—
Coleman Junction—
Cisco—

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