WELL · 42-041-30874 · DISTRICT 3

Dix Ransom #1

Plugged

Brazos County · Stone City (Austin Chalk) field  · Vertical

Dix Ransom #1 (API 42-041-30874) is a plugged well in Brazos County, plugged May 28, 2013, last operated by Amoco Production Company.

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

Completion filings report 3 formation tops, including Austin Chalk, Buda, Georgetown.

Its 2 leases have reported 61.4K barrels of oil and 107K mcf of gas since January 1993, last reporting in November 2013.

Operator of record

Amoco Production Company

Houston, TX · P-5 Y, filed May 7, 2004 · 7,201 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAmoco Production Company
Production reportsApache Corporationthrough Jul 2012
Latest permitAmoco Production CompanyApr 5, 1989

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
Apr 5, 1989
last permit issued
Jun 23, 1983
completed
61.4K
cumulative oil, bbl
107K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Nov 2013

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 23, 1983
Shut in
—
Plugged
May 28, 2013

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Dix, Ransom O-3-20885Caldwell (Austin Chalk)Apache Corporation161.4K107KJan 1993 – Nov 2013
— O-3-16786——000—

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. 1MW Petroleum CorporationJan 1993 → Aug 1998
  2. 2Apache CorporationSep 1998 → Jul 2012

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
356420-99RecompletionAmoco Production CompanyFeb 27, 1989Apr 5, 1989—7,876
193848-99DrillAmoco Production CompanyMay 2, 1983May 2, 1983Jun 5, 19838,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-16786————
—— O-3-20885————

Formation tops

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

FormationMD ftSubsea
Austin Chalk7,064-6,817
Buda7,598-7,351
Georgetown7,676-7,429

Perforations

Perforated and open-hole intervals.

FromToType
7,1357,164Perforated
7,1357,205Perforated
7,1717,178Perforated
7,1837,205Perforated
7,6187,627Perforated
7,6307,638Perforated
7,7007,720Perforated
7,7407,750Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6253,49912.252,025 S
2.8757,035——
5.57,8767.875584 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
00Feb 26, 1991Sep 22, 1989—
00Jan 30, 1991Jul 27, 1983—
00Jan 12, 1984Jul 27, 1983—

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