WELL · 42-273-32191 · DISTRICT 4

King Ranch Tijerina #1137J

Plugged

Kleberg County · T-C-B (Lower Vicksburg) field  · Vertical

King Ranch Tijerina #1137J (API 42-273-32191) is a plugged well in Kleberg County, plugged December 28, 2000, last operated by Exxon Corp..

The RRC has issued 2 drilling permits between 1993 and 1994, permitted to 11,300 ft.

Completion filings report 3 formation tops, including J-13, 9400 Sd, 9900 Sd.

Operator of record

Exxon Corp.

Based in
Houston, TX
P-5 status
See remarks (S)
P-5 last filed
Mar 15, 1999
Permits on file
19,549
Phone
(713) 431-1125

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleExxon Corp.
Production reportsExxon Mobil Corporationthrough Oct 2000
Latest permitExxon Corp.Oct 21, 1994

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

11,300
total depth, ft
2
permits on file
Oct 21, 1994
last permit issued
Sep 29, 1993
completed
0
cumulative oil, bbl
488K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 1993 THROUGH Dec 2000

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 29, 1993
Shut in
—
Plugged
Dec 28, 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 Tijerina G-4-151723Tijerina-Canales-Blucher ( J-43)Exxon Mobil Corporation10231KOct 1994 – Dec 2000
King Ranch Tijerina G-4-147945T-C-B (Lower Vicksburg)Exxon Corp.10257KSep 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. 1Exxon Corp.Oct 1993 → Mar 2000
  2. 2Exxon Mobil CorporationApr 2000 → Oct 2000

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
429298-99RecompletionExxon Corp.Oct 21, 1994Oct 21, 1994Oct 18, 19948,844
413813-99DrillExxon Corp.Jul 13, 1993Jul 13, 1993Jul 19, 199311,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-147945————
—— G-4-151723————

Formation tops

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

FormationMD ftSubsea
J-138,785-8,637
9400 SD9,310-9,162
9900 SD9,582-9,434

Perforations

Perforated and open-hole intervals.

FromToType
7,4717,482Perforated
8,7908,800Perforated
9,5829,799Perforated
9,9549,969Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3752,03817.51,540 S
9.6257,99812.251,750 S
5.510,3906.75327 S
510,3906.75327 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
00Jan 18, 2000Dec 15, 1999—
00Jun 19, 1995May 11, 1995—
00Feb 28, 1995Nov 22, 1994Yes
00Nov 29, 1994——
00Mar 21, 1994Jan 12, 1994Yes
00Feb 9, 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/27332191, documented in the API reference.