TEXAS · WELLS · THROCKMORTON COUNTY · API 42-447-33768 · DISTRICT 6E
Daws F. 1687 #1
Throckmorton County · Tuttle field · Vertical
Daws F. 1687 #1 (API 42-447-33768) is a plugged well in Throckmorton County, plugged January 29, 1988, last operated by Ashtola Exploration Company Inc..
The RRC has issued 3 drilling permits between 1983 and 1986, permitted to 4,800 ft.
Completion filings report 3 formation tops, including King Sand, Tuttle Sand, Caddo.
Operator of record
Ashtola Exploration Company Inc.
- Based in
- Amarillo, TX
- P-5 status
- Delinquent (D)
- P-5 last filed
- Feb 2, 2016
- Permits on file
- 362
- Phone
- (806) 376-4371
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Ashtola Exploration Company Inc. |
| Production reports | none |
| Latest permit | Ashtola Exploration Company,inc.Sep 30, 1986 |
- 4,800
- total depth, ft
- 3
- permits on file
- Sep 30, 1986
- last permit issued
- Apr 25, 1987
- completed
- —
- cumulative oil, bbl
- —
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Apr 25, 1987
- Shut in
- —
- Plugged
- Jan 29, 1988
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.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 321217-99 | Recompletion | Ashtola Exploration Company,inc. | Sep 29, 1986 | Sep 30, 1986 | — | 3,200 |
| 207567-99 | Drill | Ashtola Exploration Company,inc. | Apr 2, 1984 | Aug 25, 1983 | Feb 6, 1984 | 3,885 |
| 207566-99 | Drill | Ashtola Exploration Company,inc. | Aug 12, 1983 | Aug 25, 1983 | — | 4,800 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Apr 25, 1987 | Daws F. 1687 O-8-24343 | Tuttle | Ashtola Exploration Company Inc. | Plugged | — |
| Mar 1, 1984 | Daws F. 1687 G-13-110588 | Daws (King Sand) | Ashtola Exploration Company Inc. | Plugged | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,214 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| King Sand | 521 | 693 |
| Tuttle Sand | 3,110 | -1,896 |
| Caddo | 3,850 | -2,636 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 521 | 525 | Perforated |
| 3,111 | 3,122 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 161 | 12.25 | 140 sx |
| 7 | 1,142 | 7.875 | 100 sx |
| 4.5 | 3,231 | 7.875 | 125 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jun 9, 1987 | May 7, 1987 | Yes |
| 00 | Jun 1, 1987 | — | — |
| 00 | May 31, 1984 | Mar 30, 1984 | — |
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-447-33768 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-447-33768 → scanned completion filings
Log images filed since 2004 open from the RRC's log search for this well; none are loaded here for it.
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/44733768, documented in the API reference.