TEXAS · WELLS · JEFFERSON COUNTY · DANUBE LEASE · API 42-245-32710 · DISTRICT 03

Danube #1

Plugged

Jefferson County · Wildcat field  · Directional

Danube #1 (API 42-245-32710) is a plugged well in Jefferson County, plugged August 8, 2014, last operated by Cimarex Energy CO..

The RRC has issued one drilling permit (amended once), issued September 2, 2011, permitted to 16,000 ft.

Operator of record

Cimarex Energy Co.

Based in
Midland, TX
P-5 status
Delinquent (D)
P-5 last filed
Jul 8, 2025
Permits on file
2,082
Phone
(432) 571-7800

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCimarex Energy Co.
Production reportsnone
Latest permitCimarex Energy Co.Sep 2, 2011
16,000
total depth, ft
2
permits on file
Sep 2, 2011
last permit issued
Nov 24, 2011
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 2011 THROUGH —

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Nov 24, 2011
Shut in
—
Plugged
Aug 8, 2014

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Danube G-3-266999WildcatCimarex Energy Co.100Nov 2011 – —

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
723146-98DrillCimarex Energy Co.Sep 16, 2011Sep 2, 2011Oct 10, 201116,000
723146-99DrillCimarex Energy Co.Aug 26, 2011Sep 2, 2011Oct 10, 201116,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Nov 24, 2011Danube G-3-266999WildcatCimarex Energy Co.Plugged—

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3754,37117.53,910 S
9.62511,10012.251,220 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Apr 8, 2013Oct 25, 2012Yes

Well logs

1 log loaded from the RRC's log index, the latest received Nov 21, 2014. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
RESISTIVITYTIFF4,388 to 16,320Nov 21, 2014run Nov 16, 20113.75

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

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