WPR14CA193 · Kalman George LANCAIR 360
Kalman George LANCAIR 360 · Accident: hard landing
From Albuquerque International Sunport (ABQ) to Grand Canyon National Park Airport (GCN)
Event
- NTSB case
- WPR14CA193
- 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
- 0
- 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
Kalman George LANCAIR 360
- Aircraft type
- Kalman George LANCAIR 360
- 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
- N521SH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Albuquerque International Sunport (ABQ), Albuquerque, NMTo Grand Canyon National Park Airport (GCN), Grand Canyon, AZ
- Aircraft age
- About 17 years (built 1997)
- 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
- Landing · flare/touchdown
- 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
- Hard landing
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he entered a right traffic pattern and established 80 knots on final approach. During the final approach he reduced engine power to idle and began to flare the airplane. The pilot stated that he believed that he flared higher than normal and he held a steady pitch attitude. As the airspeed decreased the airplane unexpectedly dropped and impacted the runway hard. The pilot lost directional control and the airplane skidded off the runway into a grassy area. The subsequent impact resulted in substantial damage to the lower fuselage and rudder. The pilot report no preimpact malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot's inadequate flare, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR14CA193
- Event ID
- 20140516X40521
- Case number
- WPR14CA193
- 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. 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: 32d0f5776882c67ba36255b3331430acea0ee037d971d5245c2e61c3a9d42872; retrieved 2026-09-15T23:37:54.744Z.