WELL · 42-473-30786 · DISTRICT 3

Koomey #1

Y

Waller County · Brookshire field · Temp Abandoned  · Vertical

Koomey #1 (API 42-473-30786) is a well in Waller County operated by Silverbrook Operating LLC, completed December 9, 2002 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued November 13, 2002, permitted to 4,000 ft.

It was permitted by Property Development Group, Inc. and has since transferred to Silverbrook Operating LLC on the wellbore schedule.

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

Operator of record

Silverbrook Operating LLC

Permitted by Property Development Group, Inc.; the EWA schedule now lists a different operator.

Barker, TX · P-5 Y, filed Jul 4, 2026 · (713) 410-2385

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSilverbrook Operating LLC
Production reportsProperty Development Group, Inc.through Nov 2003
Latest permitProperty Development Group, Inc.Nov 13, 2002

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
Nov 13, 2002
last permit issued
Dec 9, 2002
completed
0
cumulative oil, bbl
13.5K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2002 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Dec 9, 2002
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
Koomey G-3-193890Brookshire Dome (Miocene 5-1C)Silverbrook Operating, LLC1013.5KDec 2002 – 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. 1Property Development Group, Inc.Mar 2003 → Nov 2003

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
525453-99DrillProperty Development Group, Inc.Nov 13, 2002Nov 13, 2002Nov 15, 20024,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-193890————

Perforations

Perforated and open-hole intervals.

FromToType
527529Perforated
533537Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62550412.25215 S
5.53,4487.875450 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
00May 7, 2003Apr 2, 2003Yes
00Apr 24, 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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
0
bbl, all reported
Apr 2024
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000094627W-14 DisposalNot activated3,0005003,565–3,665

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

Last 12 months 0

012024

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