WELL · 42-469-33202 · DISTRICT 2

Union Keeran #11

N

Victoria County  · Vertical

Union Keeran #11 (API 42-469-33202) is a permitted well in Victoria County filed by Hart Petroleum Services, Inc; no completion report is on file yet.

The RRC has issued 3 drilling permits between 1997 and 1999, permitted to 7,100 ft.

Completion filings report 3 formation tops, including Catahoula, Greta, Sinton (Frio).

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

Operator of record

Hart Petroleum Services, Inc

Based in
Corpus Christ, TX
P-5 status
Inactive (I)
P-5 last filed
Jan 23, 2025
Permits on file
146
Phone
(361) 887-6371

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsHart Petroleum Services, Incthrough Apr 1999
Latest permitHart Petroleum Services, IncApr 6, 1999
7,100
total depth, ft
3
permits on file
Apr 6, 1999
last permit issued
—
completed
6.45K
cumulative oil, bbl
202K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 1997 THROUGH Jul 2025

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
Union Keeran O-2-8369Keeran (6300)Hart Petroleum Services, Inc16.45K31.3KApr 1998 – Jul 2025
Union Keeran G-2-162792Keeran (6150)Hart Petroleum Services, Inc10170KApr 1997 – Apr 1998

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. 1Hart Petroleum Services, IncApr 1997 → Feb 1999

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
483117-99RecompletionHart Petroleum Services, IncMar 5, 1999Apr 6, 1999—7,100
475238-99RecompletionHart Petroleum Services, IncApr 13, 1998Apr 13, 1998Apr 13, 19987,100
456317-99DrillHart Petroleum Services, IncDec 13, 1996Jan 9, 1997Mar 29, 19977,100

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-162792————
—— O-2-8369————

Formation tops

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

FormationMD ftSubsea
Catahoula3,300-3,265
Greta4,100-4,065
Sinton (Frio)4,900-4,865

Perforations

Perforated and open-hole intervals.

FromToType
4,8304,833Perforated
5,8705,876Perforated
6,2786,281Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62572812.5285 S
4.57,1267.875625 S
4.57,126—625 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
00Nov 13, 2013Mar 17, 2011—
00Jul 27, 1998Apr 28, 1998Yes
00Jun 1, 1998——
00Jun 27, 1997May 1, 1997Yes
00May 13, 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/46933202, documented in the API reference.