WELL · 42-291-32868 · DISTRICT 3
Sarah Hunt A #1
Liberty County · Cottonwood (Frio 7550) field · Vertical
Sarah Hunt A #1 (API 42-291-32868) is a plugged well in Liberty County, plugged August 15, 2018, last operated by Choice Exploration Inc..
The RRC has issued one drilling permit, issued March 22, 2012, permitted to 8,600 ft.
Completion filings report 3 formation tops, including Het, Frio, Tex W.
Its lease has reported 635 barrels of oil since May 2012, last reporting in October 2018.
Operator of record
Irving, TX · P-5 Y, filed May 3, 2024 · 160 permits on file · (817) 505-1207
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Choice Exploration Inc. |
| Production reports | Choice Exploration, Inc.through Jun 2012 |
| Latest permit | Choice Exploration, Inc.Mar 22, 2012 |
- 8,600
- total depth, ft
- 1
- permits on file
- Mar 22, 2012
- last permit issued
- May 16, 2012
- completed
- 635
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · May 2012 THROUGH Oct 2018
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- May 16, 2012
- Shut in
- —
- Plugged
- Aug 15, 2018
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 |
|---|---|---|---|---|---|---|
| Sarah Hunt 'A' O-3-25995 | Cottonwood (Frio 7550) | Choice Exploration, Inc. | 1 | 635 | 0 | May 2012 – Oct 2018 |
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.
- 1Choice Exploration, Inc.May 2012 → Jun 2012
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 735435-99 | Drill | Choice Exploration, Inc. | Mar 6, 2012 | Mar 22, 2012 | Mar 24, 2012 | 8,600 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-3-25995 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 43 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Het | 5,812 | -5,769 |
| Frio | 6,132 | -6,089 |
| Tex W | 8,360 | -8,317 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 8,005 | 8,007 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 1,304 | 12.25 | 730 S |
| 7 | 8,175 | 8.75 | 355 S |
| 4.5 | 8,500 | 6.25 | 175 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 30, 2013 | Aug 28, 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-291-32868 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-291-32868 → 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/29132868, documented in the API reference.