WELL · 42-291-32897 · DISTRICT 3

Ercums #1

Y

Liberty County · Raywood S. (Gressett Sand) field · Injection  · Vertical

Ercums #1 (API 42-291-32897) is a well in Liberty County operated by K-3 Resources LP, completed August 27, 2024 and listed as injection on the RRC schedule.

The RRC has issued one drilling permit, issued November 15, 2013, permitted to 6,000 ft.

Completion filings report one formation top, including Miocene (undifferentiated).

No lease production has been reported under this well’s leases.

It holds an active disposal or injection permit, with 87.6K barrels injected in the 12 months reported through November 2025.

Operator of record

K-3 Resources LP

Brookshire, TX · P-5 Y, filed Dec 4, 2025 · 2 permits on file · (281) 585-2817

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleK-3 Resources LP
Production reportsnone
Latest permitK-3 Resources, LPNov 15, 2013
6,000
total depth, ft
1
permits on file
Nov 15, 2013
last permit issued
Aug 27, 2024
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2013 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 27, 2024
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Ercums O-3-26649Raywood, S. (Gressett Sand)K-3 Resources, LP100Dec 2013 – Jul 2026

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
773309-99DrillK-3 Resources, LPNov 6, 2013Nov 15, 2013Nov 19, 20136,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-26649————

Formation tops

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

FormationMD ftSubsea
Miocene (undifferentiated)MIOCENE 25002,300-2,290
Miocene (undifferentiated)MIOCENE 33003,100-3,090
Miocene (undifferentiated)MIOCENE 4800.04,800-4,790
Miocene (undifferentiated)MIOCENE 49004,800-4,790

Perforations

Perforated and open-hole intervals.

FromToType
4,2284,248Perforated
4,9424,962Perforated
4,9764,996Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.751,941141,072 S
75,1649.8751,288 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
00Nov 14, 2024Oct 2, 2024—
00Jun 9, 2015May 27, 2014Yes

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

87.6K
bbl, last 12 reported months
1.24M
bbl, all reported
Nov 2025
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000102450W-14 DisposalActive15,0001,5503,100–5,000

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 87,647 · prior 12 61,571(+42%)

05K10K20242025

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