WELL · 42-041-31733 · DISTRICT 3

Kurten Milton #1

Plugged

Brazos County · Giddings (Austin Chalk-3) field  · Horizontal · Sidetrack

Kurten Milton #1 (API 42-041-31733) is a plugged horizontal well in Brazos County, plugged July 8, 1999, last operated by Osr Oil & Gas Company.

The RRC has issued 2 drilling permits between 1993 and 1995, permitted to 8,000 ft.

It was permitted by Cantro Exploration, Inc. and has since transferred to Osr Oil & Gas Company on the wellbore schedule.

Completion filings report one formation top, including Austin Chalk.

Its lease has reported 93.3K barrels of oil and 63.8K mcf of gas since October 1993, last reporting in November 1999.

Operator of record

Osr Oil & Gas Company

Permitted by Cantro Exploration, Inc.; the EWA schedule now lists a different operator.

Victoria, TX · P-5 Y, filed Dec 7, 2001 · 2 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOsr Oil & Gas Company
Production reportsCantro Exploration, Inc.through Jul 1998
Latest permitCantro Exploration, Inc.May 1, 1995

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

8,000
total depth, ft
2
permits on file
May 1, 1995
last permit issued
May 16, 1995
completed
93.3K
cumulative oil, bbl
63.8K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 1993 THROUGH Nov 1999

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 16, 1995
Shut in
—
Plugged
Jul 8, 1999

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
Kurten, Milton O-3-22233Giddings (Austin Chalk-3)Osr Oil & Gas Company193.3K63.8KOct 1993 – Nov 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. 1Cantro Exploration, Inc.Oct 1993 → Jul 1998

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
435279-99Recompletion · sidetrackCantro Exploration, Inc.Apr 27, 1995May 1, 1995May 2, 19958,000
409923-98DrillCantro Exploration, Inc.Sep 2, 1993Sep 2, 1993Sep 17, 19938,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-22233————

Formation tops

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

FormationMD ftSubsea
Austin Chalk7,650-7,303

Perforations

Perforated and open-hole intervals.

FromToType
7,9959,012Perforated
7,99510,376Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.751,01514.75500 S
7.6257,9959.875380 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
00Aug 1, 1995Jun 22, 1995Yes
00Sep 9, 1994Aug 29, 1994—
00Feb 2, 1994Dec 17, 1993Yes
00Jan 5, 1994——

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