WELL · 42-249-32558 · DISTRICT 4

Gustavo Garcia #2

Plugged

Jim Wells County · Premont (Barnsdall Sand) field  · Vertical

Gustavo Garcia #2 (API 42-249-32558) is a plugged well in Jim Wells County, plugged January 29, 2025, last operated by Progas Operating Inc.

The RRC has issued one drilling permit, issued April 13, 2010, permitted to 4,000 ft.

It was permitted by Kidd Production CO. and has since transferred to Progas Operating Inc on the wellbore schedule.

Completion filings report 3 formation tops, including Singer, Lower Barnsdall Sd, Caddo.

Its lease has reported 19.2K barrels of oil since July 2010, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Progas Operating Inc

Permitted by Kidd Production Co.; the EWA schedule now lists a different operator.

Based in
Red Rock, TX
P-5 status
Delinquent (D)
P-5 last filed
May 17, 2023
Permits on file
29
Phone
(512) 213-4805

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleProgas Operating Inc
Production reportsProgas Operating, Incthrough Oct 2022
Latest permitKidd Production Co.Apr 13, 2010

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

4,000
total depth, ft
1
permits on file
Apr 13, 2010
last permit issued
Jul 30, 2010
completed
19.2K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2010 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 30, 2010
Shut in
—
Plugged
Jan 29, 2025

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Gustavo Garcia O-4-13669Premont (Barnsdall Sand)Progas Operating, Inc219.2K0Jul 2010 – Jul 2026

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. 1Kidd Production Co.Aug 2010 → Nov 2014
  2. 2Progas Operating, IncDec 2014 → Oct 2022

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
694184-99DrillKidd Production Co.Apr 9, 2010Apr 13, 2010Jun 22, 20104,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-4-13669————

Formation tops

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

FormationMD ftSubsea
Singer3,146-2,940
Lower Barnsdall SD3,435-3,229
Caddo3,600-3,394

Perforations

Perforated and open-hole intervals.

FromToType
3,4353,439Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62566412.25306 S
4.53,7047.875697 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 9, 2012Jul 20, 2011Yes

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