WELL · 42-009-43232 · DISTRICT 9

Pechacek #1

Plugged

Archer County · Birdwell field  · Vertical

Pechacek #1 (API 42-009-43232) is a plugged well in Archer County, plugged December 23, 2019, last operated by Palmer Mike Oil.

The RRC has issued one drilling permit, issued October 21, 2019, permitted to 1,900 ft.

It was permitted by Palmer, Mike Oil and has since transferred to Palmer Mike Oil on the wellbore schedule.

Operator of record

Palmer Mike Oil

Permitted by Palmer, Mike Oil; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitPalmer, Mike OilOct 21, 2019

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

1,900
total depth, ft
1
permits on file
Oct 21, 2019
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 23, 2019

Surface location

33.472471, -98.913598

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Archer 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
858000-99DrillPalmer, Mike OilOct 12, 2019Oct 21, 2019Dec 20, 20191,900

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 →

4P Bar Ranch 'B'42-009-43305

2.6 KM · Palmer, John LLC · Section with this well →

Thomas Sand1,100
Megargel1,200
Gunsight1,300
Ward Sand1,500
Canyon3,000
Strawn3,800
Bryson4,400
Cisco—

10 TOPS · FIRST 8

W. T. Richardson42-009-43164

4.9 KM · Knobloch, Albert · Section with this well →

Thomas Sand540483
Gunsight1,250-227
Canyon—
Ward Sand—
Strawn—
Megargel—
Delmar—
Davidson—

10 TOPS · FIRST 8

Portwood -C-&-D-42-009-43170

5.5 KM · Myers, James B. · Section with this well →

Thomas Sand1,100
Gunsight1,400
Cisco—
Bryson—
Canyon—
Davidson—
Delmar—
Megargel—

10 TOPS · FIRST 8

R. E. Hill42-009-42862

5.8 KM · Palmer, Mike Oil · Section with this well →

Thomas Sand1,100
Megargel1,200
Gunsight1,350
Delmar—
Cisco—
Ward Sand—
Strawn—
Bryson—

10 TOPS · FIRST 8

Clark-Richardson42-009-43211

6.2 KM · Palmer, Mike Oil · Section with this well →

Thomas Sand1,100
Megargel1,200
Gunsight1,350
Bryson—
Canyon—
Cisco—
Davidson—
Delmar—

10 TOPS · FIRST 8

Reynolds42-023-31720

6.8 KM · Willowbend Investments, Inc. · Section with this well →

Coleman Junction400909
Gunsight1,040269
Tannehill1,340-31
Palo Pinto3,630-2,321
Caddo4,898-3,589
Conglomerate5,161-3,852
Mississippian5,348-4,039
Saddle Creek—

10 TOPS · FIRST 8

N.D. Goldsmith42-009-43128

7.3 KM · Myers, James B. · Section with this well →

Thomas Sand1,24040
Gunsight1,333-53
Delmar—
Ward Sand—
Strawn—
Megargel—
Davidson—
Cisco—

10 TOPS · FIRST 8

J. T. Richardson42-009-43227

7.7 KM · Palmer, Scott Oil · Section with this well →

Gunsight1,279
Ward Sand—
Thomas Sand—
Strawn—
Megargel—
Delmar—
Davidson—
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/00943232, documented in the API reference.