WELL · 42-481-35216 · DISTRICT 3

Groesbeck Heirs #1

Plugged

Wharton County · Porter S Creek (Yegua) field  · Vertical

Groesbeck Heirs #1 (API 42-481-35216) is a plugged well in Wharton County, plugged May 26, 2022, last operated by Faulconer Energy LLC.

The RRC has issued one drilling permit (amended once), issued October 24, 2011, permitted to 8,200 ft.

It was permitted by Ricochet Energy, Inc. and has since transferred to Faulconer Energy LLC on the wellbore schedule.

Completion filings report 4 formation tops, including Vicksburg, Yegua, Top Uppers Porters Creek, Upper Porters Creek.

Operator of record

Faulconer Energy LLC

Permitted by Ricochet Energy, Inc.; the EWA schedule now lists a different operator.

Based in
Tyler, TX
P-5 status
Active (A)
P-5 last filed
Oct 29, 2025
Permits on file
46
Phone
(903) 581-4382

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleFaulconer Energy LLC
Production reportsRicochet Energy, Inc.through Jun 2015
Latest permitRicochet Energy, Inc.Oct 24, 2011

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

8,200
total depth, ft
2
permits on file
Oct 24, 2011
last permit issued
Nov 30, 2011
completed
0
cumulative oil, bbl
581K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 2011 THROUGH May 2022

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Nov 30, 2011
Shut in
—
Plugged
May 26, 2022

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Groesbeck Heirs G-3-265473Porter's Creek (Yegua)Faulconer Energy, LLC10581KNov 2011 – May 2022

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. 1Ricochet Energy, Inc.Jan 2012 → Jun 2015

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
726649-98DrillRicochet Energy, Inc.Oct 25, 2011Oct 24, 2011Oct 28, 20118,200
726649-99DrillRicochet Energy, Inc.Oct 19, 2011Oct 24, 2011Oct 28, 20118,200

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-265473————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
VicksburgTOP VICKSBURG5,310
Vicksburg5,310
YeguaTOP YEGUA6,615
Yegua6,615
Top Uppers Porters Creek7,290
Upper Porters Creek7,290

Perforations

Perforated and open-hole intervals.

FromToType
7,6377,649Perforated
7,6377,659Perforated
7,6597,685Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.752,02514.751,048 S
7.6255,9279.875358 S
4.57,8806.75391 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
00Oct 22, 2014Mar 21, 2014—
00Dec 11, 2012Feb 28, 2012Yes

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