WELL · 42-275-32372 · DISTRICT 13

Jungman #2

Plugged

Knox County · Jarvis (Tannehill) field  · Vertical

Jungman #2 (API 42-275-32372) is a plugged well in Knox County, plugged March 25, 2024, last operated by Covenant Operating LLC.

The RRC has issued one drilling permit, issued February 16, 2024, permitted to 3,000 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, LLCFeb 16, 2024

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

3,000
total depth, ft
1
permits on file
Feb 16, 2024
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
Mar 25, 2024

Surface location

33.458177, -99.705539

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Knox 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
897351-99DrillCovenant Operating, LLCFeb 13, 2024Feb 16, 2024Mar 22, 20243,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 →

Jungman42-275-32329

0.2 KM · Gunn Oil Company · Section with this well →

Frye2,022-528
Tannehill2,128-634
Mississippian—
Saddle Creek—
Strawn—
Cisco—
Home Creek—
Bend—

10 TOPS · FIRST 8

Myers42-275-32326

0.9 KM · Gunn Oil Company · Section with this well →

Coleman Junction1,556-54
Frye2,037-535
Canyon—
Cisco—
Tannehill—
Caddo—
Saddle Creek—
Strawn—

10 TOPS · FIRST 8

Styles42-275-32327

10.0 KM · HW Operating, LLC · Section with this well →

Coleman Junction1,45424
Tannehill2,000-522
Saddle Creek2,088-610
Bend—
Caddo—
Canyon—
Cisco—
Frye—

10 TOPS · FIRST 8

Dianne42-275-32349

10.5 KM · Teal Exploration, LLC · Section with this well →

Coleman Junction1,148328
Tannehill1,908-432
Saddle Creek—
Home Creek—
Frye—
Canyon—
Caddo—
Bend—

10 TOPS · FIRST 8

Dianne42-275-32340

10.5 KM · Teal Exploration, LLC · Section with this well →

Coleman Junction1,108365
Frye1,500-27
Tannehill1,906-433
Bend—
Strawn—
Saddle Creek—
Home Creek—
Cisco—

10 TOPS · FIRST 8

Dianne42-275-32336

10.7 KM · Teal Exploration, LLC · Section with this well →

Coleman Junction1,081392
Tannehill1,909-436
Saddle Creek2,008-535
Canyon—
Caddo—
Home Creek—
Frye—
Bend—

10 TOPS · FIRST 8

Dianne42-275-32333

10.8 KM · Teal Exploration, LLC · Section with this well →

Coleman Junction1,083384
Tannehill1,909-442
Strawn—
Saddle Creek—
Home Creek—
Frye—
Cisco—
Canyon—

10 TOPS · FIRST 8

Dianne42-275-32353

10.9 KM · Teal Exploration, LLC · Section with this well →

Coleman Junction1,120350
Frye1,504-34
Tannehill1,920-450
Cisco—
Canyon—
Caddo—
Home Creek—
Saddle Creek—

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