WELL · 42-125-31375 · DISTRICT 8

Pitchfork Qqqq #1

Plugged

Dickens County · Wildcat field  · Vertical

Pitchfork Qqqq #1 (API 42-125-31375) is a plugged well in Dickens County, plugged May 7, 2019, last operated by Medders Oil Company Inc..

The RRC has issued one drilling permit, issued February 14, 2019, permitted to 4,350 ft.

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

Operator of record

Medders Oil Company Inc.

Permitted by Medders Oil Company, Inc.; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitMedders Oil Company, Inc.Feb 14, 2019

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

4,350
total depth, ft
1
permits on file
Feb 14, 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
May 7, 2019

Surface location

33.540999, -100.668791

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Dickens 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
849811-99DrillMedders Oil Company, Inc.Feb 8, 2019Feb 14, 2019Apr 25, 20194,350

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 →

Sjwf42-125-31405

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

Coleman Junction4,000-1,712
Tannehill4,634-2,346
Canyon—
Atkins—

Sjwf42-125-31399

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

Coleman Junction1,360936
Tannehill4,636-2,340
Atkins—
Canyon—

Pitchfork Otoe42-125-31428

9.5 KM · Canan Mowrey Operating, LLC · Section with this well →

Coleman Junction3,582-1,487
T/Sedwick3,765-1,670
Tannehill4,166-2,071
T/Tannehill Lime4,209-2,114
Atkins—
Canyon—

Pitchfork-Toreador LH42-125-30667

10.5 KM · Dreyfus, Louis Natural Gas Corp · Section with this well →

Clear Fork1,440530
Tubb1,840130
Vale Shale2,240-270
Valera2,845-875
Coleman Junction3,432-1,462
B/Coleman JCT3,495-1,525
Noodle Creek3,875-1,905
Stockwether LS3,915-1,945

19 TOPS · FIRST 8

Pitchfork-Toreador LS42-125-30681

11.1 KM · Dreyfus, Louis Natural Gas Corp · Section with this well →

Valera2,762-899
Noodle Creek Lime3,784-1,921
Stockwether Lime3,819-1,956
Tannehill3,880-2,017
Tannehill3,900-2,037
Tannehill3,940-2,077

Holly42-125-31409

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

Coleman Junction1,740547
Tannehill4,678-2,391
Canyon—
Atkins—

Neaves42-125-31369

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

Coleman Junction2,800
Tannehill4,812
Canyon—
Atkins—

Pitchfork Tttt42-269-33051

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

Coleman Junction3,238-1,249
Tannehill3,777-1,788
Canyon—
Cisco—
Caddo—
Conglomerate—
Des Moines—
Pennsylvanian—

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