CEN09CA465 · Piper PA32R 301T
Piper PA32R 301T · Accident: windshear or thunderstorm during takeoff
From City of Colorado Springs Municipal Airport (KCOS) to Amarillo, TX
Event
- NTSB case
- CEN09CA465
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA32R 301T
- Aircraft type
- Piper PA32
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N301RT
- Operator
- Dean Sather
- Onboard fatalities
- Unknown
- Route
- From City of Colorado Springs Municipal Airport (KCOS), Colorado Springs, COTo Amarillo, TX
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Takeoff
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Windshear or thunderstorm
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Environmental issues › Conditions/weather/phenomena
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
According to the pilot, the tower controller cautioned for wind shear and then cleared the flight to depart. The pilot delayed momentarily to assess the wind conditions and then departed. The airplane climbed to 75 feet, and then began to lose altitude as if the airplane was "being pushed down." The pilot applied corrective measures but was unable to arrest the descent. The airplane impacted the runway resulting in substantial damage to the airplane. The automated special weather observation report, issued shortly after the time of the accident, reported winds variable from 100 degrees to 160 degrees at 7 knots with light rain.
Probable cause
The pilot's low altitude encounter with windshear during takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN09CA465
- Event ID
- 20090727X43538
- Case number
- CEN09CA465
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 131bcb2edb26a5077e56ca6354c14def8629c3a70daae7160ccfc7a2b8e193ff; retrieved 2026-09-15T12:02:12.918Z.