WPR14CA386 · Cessna Aircraft Co E162 UNDESIGNAT
Rainier Flight Service Cessna Aircraft Co E162 UNDESIGNAT · Accident: abnormal runway contact during landing
From Renton Municipal Airport (KRNT) to Bellingham International Airport (KBLI)
Event
- NTSB case
- WPR14CA386
- 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
Cessna Aircraft Co E162 UNDESIGNAT
- Aircraft type
- Cessna 162
- 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
- N6035S
- Operator
- Rainier Flight Service
- Onboard fatalities
- Unknown
- Route
- From Renton Municipal Airport (KRNT), Renton, WATo Bellingham International Airport (KBLI), Bellingham, WA
- Aircraft age
- About 3 years (built 2011)
- 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
- Abnormal runway contact
- 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 student pilot planned to conduct a solo cross-country flight to another towered airport. His preflight inspection, engine start and runup, takeoff, and flight of the special light-sport airplane were all uneventful. When he neared the destination airport, he was instructed to enter the traffic pattern on the downwind leg for runway 16. He was subsequently cleared for "closed traffic" pattern work, and instructed to follow another airplane. The pilot informed the air traffic controller that he intended to do a full stop landing, and shortly thereafter, was instructed to turn base leg. He selected full flaps (40 degrees) for landing after turning final. According to the pilot, the wind was from 180 degrees at 7 knots, and the airplane was "just a little" to the right of the centerline for part of the last segment of the final approach. The pilot flared for landing, and the airplane touched down on the main gear, but then "ballooned" back airborne. The airplane bounced again, and then on the third bounce, the nose landing gear failed. The airplane slid to a stop on the runway. The airplane sustained substantial damage to the fuselage structure. During the bounce sequence, the pilot only used the control wheel to attempt to control and stop the bounces; he did not vary the throttle setting. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot's inadequate flare and failure to maintain aircraft control during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR14CA386
- Event ID
- 20140924X42217
- Case number
- WPR14CA386
- 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: 49835e0d07bafa0cb914d5da08fb97de343852cb5e1c819e5a0d578554db67c5; retrieved 2026-09-16T01:48:02.852Z.