WELL · 42-703-30369 · DISTRICT 4

State Tract 845-S M-77220 #1

N

Matgrda IS-LB County  · Directional

State Tract 845-S M-77220 #1 (API 42-703-30369) is a permitted well in Matgrda IS-LB County filed by Choctaw II Oil & Gas, Ltd.; no completion report is on file yet.

The RRC has issued 3 drilling permits (amended once) between 1979 and 1991, permitted to 7,700 ft.

Its 3 leases have reported 290K barrels of oil and 125K mcf of gas since January 1993, last reporting in February 2000. The leases carry 3 wells, so these are lease totals, not this well alone.

Operator of record

Choctaw II Oil & Gas, Ltd.

Houston, TX · P-5 Y, filed May 3, 2002 · 5 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsChoctaw II Oil & Gas, Ltd.through Dec 1998
Latest permitChoctaw II Oil & Gas, Ltd.Mar 20, 1991
7,700
total depth, ft
4
permits on file
Mar 20, 1991
last permit issued
—
completed
290K
cumulative oil, bbl
125K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Feb 2000

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
State Tract 845-S M-77220 O-4-11891Matagorda Isl. BLK 721-L (15)Choctaw II Oil & Gas, Ltd.2290K93.1KJan 1993 – Feb 2000
State Tract 845-S (M-77220) G-4-95286Matagorda Isl. BLK 721-L (17-19)Choctaw II Oil & Gas, Ltd.1032.4KJan 1993 – Nov 1999
— G-4-95289——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. 1Choctaw II Oil & Gas, Ltd.Jan 1993 → Dec 1998

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
385822-99RecompletionChoctaw II Oil & Gas, Ltd.Mar 18, 1991Mar 20, 1991—7,700
378828-98RecompletionChoctaw II Oil & Gas, Ltd.Mar 18, 1991Jan 25, 1991Jan 16, 19917,700
378828-99RecompletionChoctaw II Oil & Gas, Ltd.Oct 2, 1990Jan 25, 1991—7,700
43166-99DrillOXY Petr. IncFeb 26, 1979Feb 26, 1979May 8, 19797,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-95286————
—— G-4-95289————
—— O-4-11891————

Perforations

Perforated and open-hole intervals.

FromToType
6,9456,949Perforated
7,1927,202Perforated
7,2447,256Perforated
7,3947,444Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
20140——
20142——
20230——
10.752,93014.75—
10.752,930——
10.752,94914.751,700 S
2.3757,185——
2.3757,386——
7.6257,7009.875600 S
7.6257,7007.875875 S
7.6257,700——

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
00Oct 3, 1991Feb 14, 1991Yes
00Sep 20, 1991Feb 22, 1991Yes
00Jun 20, 1991—Yes
00Jan 12, 1984Jul 27, 1981—

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