WELL · 42-049-33065 · DISTRICT 7

SRC-Garms/Leatherwood 'A' #1

N

Brown County  · Vertical

Src-Garms/Leatherwood 'A' #1 (API 42-049-33065) is a permitted well in Brown County filed by Bayou Operating Company, Inc.; no completion report is on file yet.

The RRC has issued 3 drilling permits between 1982 and 2011, permitted to 3,500 ft.

Completion filings report 3 formation tops, including Cross Cut Sand, Caddo, Duffer.

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

Operator of record

Bayou Operating Company, Inc.

Abilene, TX · P-5 Y, filed Jul 4, 2026 · 37 permits on file · (325) 668-0059

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsBayou Operating Company, Inc.through Apr 2026
Latest permitBayou Operating Company, Inc.May 17, 2011
3,500
total depth, ft
3
permits on file
May 17, 2011
last permit issued
—
completed
1.45K
cumulative oil, bbl
13K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

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
SRC-Garms/Leatherwood "A" G-8-262282Brown County RegularBayou Operating Company, Inc.1011.8KFeb 2011 – Jul 2026
SRC Garms/Leatherwood "A" O-8-19297Jett (Ellenburger)Bayou Operating Company, Inc.21.45K1.14KJan 1993 – Mar 2012

Gas, mcf lease total

Last 12 months 377 · prior 12 436(-14%)

0100200300202420252026

Chain of custody

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

  1. 1JKW Energy DivisionJan 1993 → Dec 2003
  2. 2Bayou Operating Company, Inc.Mar 2011 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
714699-99RecompletionBayou Operating Company, Inc.Apr 20, 2011May 17, 2011Feb 1, 20113,395
227932-99RecompletionGrand Banks Energy CompanyJan 30, 1984Jan 31, 1984—3,395
152211-99DrillGrand Banks Energy CompanyMar 3, 1982Mar 3, 1982—3,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-262282————
—— O-8-19297————

Formation tops

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

FormationMD ftSubsea
Cross Cut Sand1,118494
CaddoCADDO LIME2,048-436
Duffer3,078-1,466

Perforations

Perforated and open-hole intervals.

FromToType
2,8162,878Perforated
3,3663,380Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62520011140 S
2.3753,374——
4.53,3957.875360 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
00Feb 24, 2012Sep 16, 2011—
00Jan 12, 1984Jan 17, 1983—

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