WELL · 42-219-37426 · DISTRICT 8

Blue Goose #1

Plugged

Hockley County · Weeks (Clearfork) field  · Vertical

Blue Goose #1 (API 42-219-37426) is a plugged well in Hockley County, plugged December 18, 2018, last operated by Socorro Exploration Inc..

The RRC has issued one drilling permit, issued March 22, 2018, permitted to 7,100 ft.

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

Operator of record

Socorro Exploration Inc.

Permitted by Socorro Exploration, Inc.; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitSocorro Exploration, Inc.Mar 22, 2018

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

7,100
total depth, ft
1
permits on file
Mar 22, 2018
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
Dec 18, 2018

Surface location

33.802526, -102.229356

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Hockley 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
837865-99DrillSocorro Exploration, Inc.Mar 22, 2018Mar 22, 2018—7,100

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 →

Weeks A42-219-37535

3.6 KM · Seaboard Operating Co. · Section with this well →

Santa Rosa1,1302,288
Yates2,3811,037
San Andres3,510-92
Clear Fork5,552-2,134
Strawn—
Canyon—
Cisco—
Abo—

10 TOPS · FIRST 8

Hezzie Carson42-219-37494

6.3 KM · Texland Petroleum, L.P. · Section with this well →

Santa Rosa1,1402,299
Yates2,441998
San Andres3,583-144
Clear Fork6,539-3,100
Canyon—
Abo—
Wolfcamp—
Wichita-Albany—

10 TOPS · FIRST 8

Jeffers42-219-37545

7.8 KM · Texland Petroleum, L.P. · Section with this well →

Rustler1,9521,475
Yates2,469958
Glorieta5,186-1,759
Clear Fork6,557-3,130
Santa Rosa—
Wolfcamp—
Wichita-Albany—
San Andres—

10 TOPS · FIRST 8

Newton 105-142-219-37445

7.8 KM · SHP Energy Corp. · Section with this well →

Yates2,2571,138
Seven Rivers2,455940
Queen2,982413
Grayburg3,240155
San Andres3,35144
PI Shale4,103-708
Glorieta4,969-1,574
Clear Fork5,586-2,191

10 TOPS · FIRST 8

Jeffers42-219-37493

8.0 KM · Texland Petroleum, L.P. · Section with this well →

Santa Rosa1,1432,286
Yates2,489940
San Andres3,644-215
Clear Fork6,689-3,260
Abo—
Canyon—
Wolfcamp—
Strawn—

10 TOPS · FIRST 8

Newton 105-142-219-37447

8.3 KM · SHP Energy Corp. · Section with this well →

Yates2,2551,140
Seven Rivers2,452943
Queen2,980415
Grayburg3,241154
San Andres3,36827
PI Shale4,110-715
Glorieta4,980-1,585
Clear Fork5,563-2,168

10 TOPS · FIRST 8

Pair42-219-31947

8.4 KM · Texland Petroleum, L.P. · Section with this well →

Clear Fork6,750-3,316
Clear Fork6,860-3,426

White42-219-37526

9.0 KM · Texland Petroleum, L.P. · Section with this well →

Rustler1,9651,475
Yates2,505935
Glorieta5,216-1,776
Clear Fork6,586-3,146
Santa Rosa—
Abo—
Cisco—
Wolfcamp—

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