WELL · 42-175-32970 · DISTRICT 2

Danklefs #1

N

Goliad County  · Vertical

Danklefs #1 (API 42-175-32970) is a permitted well in Goliad County filed by Carrizo Oil & Gas, Inc.; no completion report is on file yet.

The RRC has issued 2 drilling permits between 1997 and 2002, permitted to 9,000 ft.

Completion filings report 4 formation tops, including Slick, Luling, Mackhank, Massive.

Its 2 leases have reported 200 barrels of oil and 344K mcf of gas since April 1997, last reporting in March 2000. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Carrizo Oil & Gas, Inc.

Based in
Houston, TX
P-5 status
Inactive (I)
P-5 last filed
Jan 7, 2021
Permits on file
1,194
Phone
(713) 328-1000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsTri-Union Development Corp.through Jul 1999
Latest permitCarrizo Oil & Gas, Inc.Jun 10, 2002
9,000
total depth, ft
2
permits on file
Jun 10, 2002
last permit issued
—
completed
200
cumulative oil, bbl
344K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 1997 THROUGH Mar 2000

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Danklefs O-2-8450Eustace Creek (Slick)Tri-Union Development Corp.1200300Mar 1999 – Mar 2000
Danklefs G-2-163316Eustace Creek (Slick)Tri-Union Development Corp.10344KApr 1997 – Sep 1999

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

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Teco Oil & Gas, Inc.Apr 1997 → Nov 1997
  2. 2Tri-Union Development Corp.Dec 1997 → Jul 1999

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
520835-99ReenterCarrizo Oil & Gas, Inc.Jun 10, 2002Jun 10, 2002—9,000
460057-99DrillTeco Oil & Gas, Inc. -Mar 19, 1997Mar 19, 1997Mar 25, 19978,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-163316————
—— O-2-8450————

Formation tops

As filed on W-2/G-1. Subsea from 330 ft elevation.Download CSV →

FormationMD ftSubsea
Slick7,884-7,554
Luling8,015-7,685
Mackhank8,126-7,796
Massive8,190-7,860

Perforations

Perforated and open-hole intervals.

FromToType
7,8837,898Perforated
7,8837,908Perforated
7,8838,144Perforated
7,9137,922Perforated
8,1288,132Perforated
8,1388,144Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,63812.25651 S
5.58,2607.875241 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. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jul 30, 1999Mar 3, 1999—
00Jul 28, 1999Mar 3, 1999—
00Jul 27, 1999Jun 10, 1999—
00Jun 30, 1999——
00Aug 26, 1997May 23, 1997Yes
00Jul 3, 1997——

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.

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