WELL · 42-321-32303 · DISTRICT 3
Sugar Valley #1
Matagorda County · Sugar Valley SE. (Text. 2) field · Vertical
Sugar Valley #1 (API 42-321-32303) is a plugged well in Matagorda County, plugged December 8, 2022, last operated by Texakoma E & P LLC.
The RRC has issued one drilling permit, issued March 24, 2010, permitted to 13,500 ft.
Completion filings report 2 formation tops, including Miocene (undifferentiated), Frio.
Operator of record
- Based in
- Plano, TX
- P-5 status
- Active – Extension (X)
- P-5 last filed
- Nov 24, 2025
- Permits on file
- 102
- Phone
- (972) 701-9106
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Texakoma E & P LLC |
| Production reports | Texakoma E & P, LLCthrough Nov 2019 |
| Latest permit | Texakoma E & P, LLCMar 24, 2010 |
- 13,500
- total depth, ft
- 1
- permits on file
- Mar 24, 2010
- last permit issued
- May 14, 2012
- completed
- 0
- cumulative oil, bbl
- 452K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · May 2012 THROUGH Dec 2022
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- May 14, 2012
- Shut in
- —
- Plugged
- Dec 8, 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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Sugar Valley G-3-270952 | Sugar Valley, SE. (Text. 2) | Texakoma E & P, LLC | 1 | 0 | 452K | May 2012 – Dec 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.
- 1Texakoma E & P, LLCNov 2012 → Nov 2019
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 693373-99 | Drill | Texakoma E & P, LLC | Mar 24, 2010 | Mar 24, 2010 | Mar 23, 2012 | 13,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-3-270952 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 32 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Miocene (undifferentiated)MIOCENE | 3,000 | -2,968 |
| FrioUPPER FRIO | 8,000 | -7,968 |
| FrioLOWER FRIO | 11,400 | -11,368 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 12,420 | 12,456 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 10.75 | 3,200 | 14.75 | 1,216 S |
| 7.625 | 11,502 | 9.875 | 493 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 | Jan 9, 2014 | Dec 3, 2012 | Yes |
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-321-32303 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-321-32303 → 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/32132303, documented in the API reference.