WELL · 42-269-33012 · DISTRICT 8

Laguna Madre #1

Plugged

King County · Wildcat field  · Directional

Laguna Madre #1 (API 42-269-33012) is a plugged well in King County, plugged November 27, 2022, last operated by Burnett Oil CO. Inc..

The RRC has issued one drilling permit, issued October 27, 2022, permitted to 9,000 ft.

It was permitted by Burnett Oil CO., Inc. and has since transferred to Burnett Oil CO. Inc. on the wellbore schedule.

Operator of record

Burnett Oil Co. Inc.

Permitted by Burnett Oil Co., Inc.; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitBurnett Oil Co., Inc.Oct 27, 2022

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

9,000
total depth, ft
1
permits on file
Oct 27, 2022
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 27, 2022

Surface location

33.623889, -100.395833

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
884965-99DrillBurnett Oil Co., Inc.Oct 17, 2022Oct 27, 2022Nov 18, 20229,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 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 →

Pearls42-269-33067

4.2 KM · Halliburton Operating Company · Section with this well →

Coleman Junction1,400458
Tannehill3,420-1,562
Cisco3,540-1,682
Canyon—
Pennsylvanian—
Bunger—
Caddo—
Des Moines—

10 TOPS · FIRST 8

Somervell 666642-269-33049

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

Coleman Junction3,025-1,025
Tannehill3,752-1,752
Caddo—
Strawn—
Pennsylvanian—
Des Moines—
Conglomerate—
Cisco—

10 TOPS · FIRST 8

Pitchfork Parker42-269-32976

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

Coleman Junction3,188-1,167
Cisco3,680-1,659
Tannehill3,770-1,749
Canyon—
Caddo—
Bunger—
Strawn—
Pennsylvanian—

10 TOPS · FIRST 8

Pitchfork42-269-33050

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

Coleman Junction3,084-1,057
Tannehill3,769-1,742
Pennsylvanian—
Des Moines—
Conglomerate—
Cisco—
Canyon—
Bunger—

10 TOPS · FIRST 8

Forks South Balt Unit42-269-32394

11.1 KM · Medders Oil Company, Inc. · Section with this well →

Coleman Junction3,076-1,140
Tannehill3,733-1,797

Four Sixes 'A'42-269-32985

11.2 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—
Tannehill—

10 TOPS · FIRST 8

Four Sixes 'B'42-269-32984

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

Coleman Junction3,030-1,088
Pennsylvanian3,030-1,088
Tannehill3,745-1,803
Cisco4,792-2,850
Bunger4,881-2,939
Canyon5,541-3,599
Des Moines5,753-3,811
Strawn5,753-3,811

10 TOPS · FIRST 8

Forks South Balt Unit42-269-32992

12.1 KM · Medders Oil Company, Inc. · Section with this well →

Coleman Junction3,115-1,109
Tannehill3,775-1,769
Tannehill3,858-1,852
Cisco—
Canyon—
Caddo—
Strawn—
Bunger—

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