WELL · 42-263-32139 · DISTRICT 8

Beggs #1101

Plugged

Kent County · Christopher (Lower Tannehill) field  · Vertical

Beggs #1101 (API 42-263-32139) is a plugged well in Kent County, plugged July 1, 2019, last operated by Covenant Operating LLC.

The RRC has issued one drilling permit, issued June 19, 2019, permitted to 4,500 ft.

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

Operator of record

Covenant Operating LLC

Permitted by Covenant Operating, LLC; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitCovenant Operating, LLCJun 19, 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,500
total depth, ft
1
permits on file
Jun 19, 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
Jul 1, 2019

Surface location

33.393472, -100.601657

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Kent 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
854197-99DrillCovenant Operating, LLCJun 13, 2019Jun 19, 2019Jun 25, 20194,500

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 →

Beggs42-263-32167

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

Wichita-Albany2,680-832
Noodle Creek3,450-1,602
Tannehill3,854-2,006
Wolfcamp3,900-2,052
Clear Fork—
Yates—
San Andres—
Rustler—

10 TOPS · FIRST 8

Pitchfork-Toreador LH42-125-30667

7.0 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

7.0 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

Hot Springs42-263-32174

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

Clear Fork1,090899
Wichita-Albany1,300689
Coleman Junction3,150-1,161
Noodle Creek3,748-1,759
Rustler—
San Andres—
Canyon—
Wolfcamp—

10 TOPS · FIRST 8

Pitchfork Otoe42-125-31428

8.1 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
Canyon—
Atkins—

Springer '196'42-269-32977

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

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

10 TOPS · FIRST 8

Springer 'A'42-269-33014

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

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

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