FTW98LA417 · Cessna 172N
Akih Air Cessna 172N · Accident: hard landing
From Flagstaff Pulliam Airport (FLG) to Gallup Municipal Airport (GUP)
Event
- NTSB case
- FTW98LA417
- 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
Cessna 172N
- Aircraft type
- Cessna 172
- 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
- N739JT
- Operator
- Akih Air
- Onboard fatalities
- Unknown
- Route
- From Flagstaff Pulliam Airport (FLG), Flagstaff, AZTo Gallup Municipal Airport (GUP)
- 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
- Landing · flare/touchdown
- First occurrenceThe 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
- Pilot in command › Flare, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot, a Nepalese national, was on a cross-country flight to satisfy a portion of the requirements for a U.S. commercial pilot certificate. When he turned onto final approach at the end of the flight, he had to increase his crab angle to compensate for a crosswind he estimated to be greater than 10 knots. He also added power to maintain airspeed. As he got closer to the runway, he noticed his airspeed was 71 knots instead of 65 knots, so he reduced power to idle. The airplane touched down hard and bounced twice. On the third bounce, the nose wheel went 'flat' and broke. A witness said he saw the airplane when it was 200 feet above the runway threshold. It was in a nose down attitude and appeared to be going 'very fast.' He said the airplane touched down, 'bounced repeatedly,' then departed the right side of the runway.
Probable cause
The pilot's inadequate landing flare. Factors were his misjudgement of altitude and his excessive airspeed.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW98LA417
- Event ID
- 20001211X11074
- Case number
- FTW98LA417
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: f3a4996f4507bfb1dfd016dd2cbc674da169de79bc4afd7f7d382b933dadc01b; retrieved 2026-09-22T16:37:11.088Z.