WELL · 42-261-00033 · DISTRICT 4

Sarita Field Oil & Gas Unit #31

N

Kenedy County  · Vertical

Sarita Field Oil & Gas Unit #31 (API 42-261-00033) is a permitted well in Kenedy County filed by Exxon Corp.; no completion report is on file yet.

The RRC has issued 6 drilling permits between 1982 and 1992, permitted to 9,000 ft.

Its 2 leases have reported 40.8K barrels of oil and 74.6K mcf of gas since January 1993, last reporting in July 2006. The leases carry 3 wells, so these are lease totals, not this well alone.

Operator of record

Exxon Corp.

Houston, TX · P-5 Y, filed Jan 3, 2003 · 19,549 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsExxon Mobil Corporationthrough Jun 2002
Latest permitExxon Corp.Apr 9, 1992
9,000
total depth, ft
6
permits on file
Apr 9, 1992
last permit issued
—
completed
40.8K
cumulative oil, bbl
74.6K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2006

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 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Sarita Field Oil & Gas Unit O-4-12061Sarita (14-E, E)Exxon Mobil Corporation140.8K74.6KJan 1993 – Jul 2006
Sarita FLD O & G Unit O-4-10876Sarita (14-F, E)Exxon Corp.200Jan 1993 – Aug 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.Jan 1993 → May 1996
  2. 2Exxon Mobil CorporationOct 2000 → Jun 2002

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
398084-99RecompletionExxon Corp.Apr 3, 1992Apr 9, 1992Jun 4, 19929,000
344267-99RecompletionExxon Corp.Mar 23, 1988Apr 19, 1988—9,000
342038-99RecompletionExxon Corp.Jan 29, 1988Feb 2, 1988—9,000
242470-99RecompletionExxon Corp.Jun 14, 1984Jun 19, 1984—9,000
228674-99RecompletionExxon Corp.Feb 7, 1984Feb 8, 1984—9,000
174182-99RecompletionExxon Corp.Oct 13, 1982Oct 13, 1982—9,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-4-10876————
—— O-4-12061————

Perforations

Perforated and open-hole intervals.

FromToType
6,2826,294Perforated
6,8456,854Perforated
6,8886,897Perforated
7,0877,093Perforated
7,4487,456Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.375948——
13.375964——
9.6252,974——
9.6253,016——
5.58,989——
5.59,000—750 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
00Sep 4, 1992Jun 23, 1992Yes
00Jul 7, 1992Jun 16, 1988Yes
00Jul 28, 1988Jun 16, 1988Yes
00Jul 23, 1988——
00Apr 23, 1985Apr 1, 1985—
00Apr 13, 1985——
00Jan 12, 1984Jul 29, 1983—
00Jan 12, 1984Jun 26, 1967—
00Jan 12, 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/26100033, documented in the API reference.