WPR18TA212 · ICP Savannah
ICP Savannah · Accident: loss of control in flight on approach
From Spanish Fork Municipal Airport/Woodhouse Field (SPK) to Primary Children's Lehi Heliport (UT99)
Event
- NTSB case
- WPR18TA212
- 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
ICP Savannah
- Aircraft type
- ICP SAVANNAH
- 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
- N951RA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Spanish Fork Municipal Airport/Woodhouse Field (SPK), Spanish Fork, UTTo Primary Children's Lehi Heliport (UT99), Fairfield, UT
- Aircraft age
- About 8 years (built 2010)
- 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
- Approach · VFR pattern base
- 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
- Loss of control in flight
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot was on a personal cross-country flight and had maneuvered the airplane onto the base leg of the traffic pattern for his destination airport. He stated that the airplane likely encountered a downdraft and experienced a loss of lift. Despite his attempts to arrest the descent by adding full throttle, the airplane impacted terrain short of the runway. The pilot thought that the accident may have been prevented if he had configured the airplane to land in a steeper and higher approach, combined with more airspeed. He reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot's failure to maintain airplane control after encountering a downdraft on approach to the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR18TA212
- Event ID
- 20180805X14725
- Case number
- WPR18TA212
- 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: dd898ca6b34d36cf285ddca496cab1cef5a573e04efabcf51a8a5cd2225c4173; retrieved 2026-09-16T08:03:03.362Z.