GAA16CA407 · Cessna 152
Hillsboro Aero Academy Cessna 152 · Accident: abnormal runway contact during landing
From Scappoose Industrial Airpark (SPB) to Scappoose Industrial Airpark (SPB)
Event
- NTSB case
- GAA16CA407
- 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 152
- Aircraft type
- Cessna 152
- 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
- N49276
- Operator
- Hillsboro Aero Academy
- Onboard fatalities
- Unknown
- Route
- From Scappoose Industrial Airpark (SPB), Scappoose, ORTo Scappoose Industrial Airpark (SPB), Scappoose, OR
- Aircraft age
- About 39 years (built 1977)
- 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 solo student pilot reported that during the third landing of his first solo, the airplane was a "little high" on final approach. He further reported that during the landing flare, the right wing was lifted by a crosswind and the airplane bounced nose wheel first on the runway. Subsequently, the nose wheel partially collapsed, the propeller struck the runway, and the airplane skidded to a stop on the runway.
The firewall sustained substantial damage.
The student pilot did not report any mechanical malfunctions or failures with the airplane that would have precluded normal operation.
The automated weather observing system (AWOS) at the airport about 7 minutes before the accident recorded the wind at 020 degrees true at 11 knots, gusting to 15 knots. The AWOS at the airport about 53 minutes after the accident recorded the wind at 330 degrees true at 8 knots. The student pilot reported that the landing was on runway 33.
Probable cause
The student pilot's failure to maintain pitch control during the landing flare in gusty crosswind conditions, which resulted in a hard landing/abnormal runway contact, a partial nose wheel collapse and substantial damage to the firewall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA407
- Event ID
- 20160802X52208
- Case number
- GAA16CA407
- 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: 3d43acf0dfc2559739ae61955351d9d362b80f6639bac1739dc05b9454b5d9b8; retrieved 2026-09-16T03:44:34.028Z.