WELL · 42-175-33309 · DISTRICT 2

Wood E #74

N

Goliad County · Sarco Creek (4700) field  · Vertical

Wood E #74 (API 42-175-33309) is a well in Goliad County operated by Charro Operating L.L.C., completed January 25, 2001.

The RRC has issued 2 drilling permits (amended once) between 2000 and 2014, permitted to 5,300 ft.

Completion filings report 3 formation tops, including Catahoula, Frio, Vicksburg.

Its 2 leases have reported 651K barrels of oil and 3.18M mcf of gas since September 1999, last reporting in July 2026. The leases carry 14 wells, so these are lease totals, not this well alone.

Operator of record

Charro Operating L.L.C.

Englewood, CO · P-5 Y, filed Feb 4, 2026 · 326 permits on file · (303) 799-9828

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCharro Operating L.L.C.
Production reportsCharro Operating, L.L.C.through Apr 2026
Latest permitCharro Operating, L.L.C.Aug 1, 2014
5,300
total depth, ft
3
permits on file
Aug 1, 2014
last permit issued
Jan 25, 2001
completed
651K
cumulative oil, bbl
3.18M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 1999 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 25, 2001
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 14 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Wood "E" O-2-8474Sarco Creek (4800)Charro Operating, L.L.C.13651K2.05MSep 1999 – Jul 2026
Wood "E" G-2-192054Sarco Creek (4700)Charro Operating, L.L.C.101.13MJan 2001 – Sep 2014

Oil, barrels lease total

Last 12 months 9,778 · prior 12 9,315(+5%)

05001K1.5K202420252026

Gas, mcf lease total

Last 12 months 10,540 · prior 12 11,399(-8%)

05001K1.5K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Charro Operating, L.L.C.Sep 1999 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
778271-99Field transferCharro Operating, L.L.C.Jan 27, 2014Aug 1, 2014Dec 13, 20005,300
502739-98DrillCharro Operating, L.L.C.Sep 19, 2002Dec 7, 2000Dec 13, 20005,300
502739-99DrillCharro Operating, L.L.C.Dec 7, 2000Dec 7, 2000—5,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-192054————
—— O-2-8474————

Formation tops

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

FormationMD ftSubsea
Catahoula2,900-2,778
Frio3,844-3,722
Vicksburg5,040-4,918

Perforations

Perforated and open-hole intervals.

FromToType
4,7984,818Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62555212.25250 S
4.55,2427.8751,075 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
00Aug 12, 2014Mar 10, 2014—
00Feb 20, 2003Aug 2, 2002Yes
00Jan 8, 2003——

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