TEXAS · WELLS · KLEBERG COUNTY · API 42-273-30408 · DISTRICT 04

King Ranch Alazan #288

Plugged

Kleberg County · Alazan North (Frio Cons.) field  · Vertical

King Ranch Alazan #288 (API 42-273-30408) is a plugged well in Kleberg County, plugged September 11, 2000, last operated by Exxon Mobil Corporation.

The RRC has issued 2 drilling permits between 1983 and 1995, permitted to 11,800 ft.

It was permitted by Exxon Corp. and has since transferred to Exxon Mobil Corporation on the wellbore schedule.

Operator of record

Exxon Mobil Corporation

Permitted by Exxon Corp.; the EWA schedule now lists a different operator.

Based in
Spring, TX
P-5 status
Active (A)
P-5 last filed
Jul 15, 2026
Permits on file
1,223
Phone
(346) 474-9142

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleExxon Mobil Corporation
Production reportsExxon Corp.through Apr 1997
Latest permitExxon Corp.Oct 16, 1995

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

11,800
total depth, ft
2
permits on file
Oct 16, 1995
last permit issued
Mar 8, 1998
completed
0
cumulative oil, bbl
240K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Sep 2000

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 8, 1998
Shut in
—
Plugged
Sep 11, 2000

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
King Ranch Alazan G-4-157699Alazan, North (J-36)Exxon Mobil Corporation10227KDec 1995 – Sep 2000
King Ranch Alazan G-4-62939Alazan, North (Deep Frio)Exxon Corp.1012.7KJan 1993 – Dec 1995

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. 1Exxon Corp.Sep 1993 → Apr 1997

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
440892-99RecompletionExxon Corp.Oct 16, 1995Oct 16, 1995Oct 24, 19959,618
213689-99RecompletionExxon Corp.Sep 16, 1983Sep 21, 1983—11,800

Completions

CompletedLeaseFieldOperatorStatusDepth
Mar 8, 1998King Ranch Alazan G-4-157699Alazan North (Frio Cons.)Exxon Mobil CorporationPlugged—
Jun 30, 1975King Ranch Alazan G-4-62939Alazan North (Deep Frio)Exxon Corp.Plugged—

Perforations

Perforated and open-hole intervals.

FromToType
9,0689,075Perforated
9,5629,568Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3752,08817.51,280 S
9.6259,33412.251,380 S
5.511,7806.75550 S
5.511,8006.75550 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
00May 6, 1998Apr 15, 1998—
00Jul 29, 1997Jul 2, 1997—
00Aug 16, 1996Jan 16, 1996Yes
00May 6, 1996——
00Jan 12, 1984Aug 11, 1975—

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