WELL · 42-469-32099 · DISTRICT 2

Horadam A #1

Plugged

Victoria County · Cologne (4570 Oil) field  · Vertical

Horadam A #1 (API 42-469-32099) is a plugged well in Victoria County, plugged April 22, 2003, last operated by Cologne Production Company.

The RRC has issued 3 drilling permits between 1983 and 2002, permitted to 5,200 ft.

Completion filings report 2 formation tops, including Discorbis, Vicksburg.

Operator of record

Cologne Production Company

San Antonio, TX · P-5 Y, filed Dec 5, 2014 · 200 permits on file · (210) 213-5414

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCologne Production Company
Production reportsCologne Production Companythrough Mar 2002
Latest permitCologne Production Co.May 1, 2002
5,200
total depth, ft
3
permits on file
May 1, 2002
last permit issued
May 3, 1984
completed
0
cumulative oil, bbl
428K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Apr 2003

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 3, 1984
Shut in
—
Plugged
Apr 22, 2003

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Horadam "A" G-2-192552Cologne (850)Cologne Production Company100May 2001 – Apr 2003
Horadam "A" G-2-133399Cologne (4570 Oil)Cologne Production Company10113KJan 1993 – Oct 2002
Horadam "A" G-2-161433Cologne (3480)Cologne Production Company10315KDec 1996 – May 2002
— O-2-6594——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. 1Cologne Production CompanyJan 1993 → Mar 2002

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
519543-99RecompletionCologne Production Co.Apr 29, 2002May 1, 2002May 3, 20024,520
456291-99RecompletionCologne Production Co.Dec 13, 1996Dec 17, 1996Dec 17, 19964,515
209987-99DrillCologne Production Co.Aug 25, 1983Sep 6, 1983Sep 24, 19835,200

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-133399————
—— G-2-161433————
—— G-2-192552————
—— O-2-6594————

Formation tops

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

FormationMD ftSubsea
Discorbis2,905-2,785
Vicksburg4,938-4,818

Perforations

Perforated and open-hole intervals.

FromToType
820834Perforated
3,4643,467Perforated
4,5704,578Perforated
4,5774,579Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62548612.25350 S
2.3754,469——
4.54,6857.875835 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 24, 2003Oct 18, 2002—
00Apr 14, 2003Oct 18, 2002Yes
00Feb 4, 2003——
00Mar 26, 1997Jan 24, 1997Yes
00Feb 10, 1997——
00Jun 11, 1990Feb 8, 1990—
00Mar 31, 1990——
00Jul 2, 1984Jun 14, 1984—
00Jan 12, 1984Jun 14, 1984—

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