TEXAS · WELLS · WALLER COUNTY · LEWIS ET AL LEASE · API 42-473-30544 · DISTRICT 03
Lewis et Al #6
Waller County · Brookshire field · Vertical
Lewis ET AL #6 (API 42-473-30544) is a plugged well in Waller County, plugged August 16, 2013, last operated by Escondido Petroleum Company Inc.
The RRC has issued one drilling permit (amended once), issued March 23, 2000, permitted to 3,600 ft.
Operator of record
Escondido Petroleum Company Inc
- Based in
- Houston, TX
- P-5 status
- Active (A)
- P-5 last filed
- Dec 23, 2025
- Permits on file
- 160
- Phone
- (713) 978-7631
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Escondido Petroleum Company Inc |
| Production reports | Escondido Petroleum Company, Incthrough Nov 2000 |
| Latest permit | Escondido Petroleum Company, IncMar 23, 2000 |
- 3,600
- total depth, ft
- 2
- permits on file
- Mar 23, 2000
- last permit issued
- Apr 4, 2000
- completed
- 0
- cumulative oil, bbl
- 8.36K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Apr 2000 THROUGH Aug 2013
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Apr 4, 2000
- Shut in
- —
- Plugged
- Aug 16, 2013
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Lewis et Al G-3-178816 | Brookshire Dome (Miocene 5-1C) | Escondido Petroleum Company, Inc | 1 | 0 | 8.36K | Apr 2000 – Aug 2013 |
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.
- 1Escondido Petroleum Company, IncJul 2000 → Nov 2000
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 493358-98 | Drill | Escondido Petroleum Company, Inc | Jul 26, 2000 | Mar 23, 2000 | Mar 23, 2000 | 3,600 |
| 493358-99 | Drill | Escondido Petroleum Company, Inc | Mar 23, 2000 | Mar 23, 2000 | — | 3,600 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Apr 4, 2000 | Lewis et Al G-3-178816 | Brookshire | Escondido Petroleum Company Inc | Plugged | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,371 | 2,373 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 415 | 12.25 | 210 S |
| 4.5 | 2,609 | 7.875 | 500 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Nov 2, 2000 | Aug 7, 2000 | Yes |
| 00 | Oct 10, 2000 | — | — |
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.
- Wellbore filings for 42-473-30544 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-473-30544 → scanned completion filings
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/47330544, documented in the API reference.