SEA85FA084 · Bellanca 17-31A
Bellanca 17-31A · Accident: hard landing
From 60S · Vancouver, WA to an unrecorded destination
Event
- NTSB case
- SEA85FA084
- 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
- 2 · 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
Bellanca 17-31A
- Aircraft type
- Bellanca 17
- 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
- N9705E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 60S · Vancouver, WATo not recorded
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/spin
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Airspeed(vs), not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WITNESSES OBSERVED THE ACFT APCH THE AIRSTRIP WITH EXCESSIVE SPEED. TOUCHDOWN ON THE RWY WAS BEYOND THE HALFWAY POINT & THE ACFT BOUNCED BACK INTO THE AIR. POWER WAS APPLIED FOR AN APPARENT GO-AROUND. THE ACFT CLEARED TALL TREES AT THE END OF THE RUNWAY, BUT CONTINUED TO MAINTAIN A NOSE-HIGH ATTITUDE, 'SHAKING AND YAWING.' THE ACFT THEN FELL OFF ON THE LEFT WING & ROLLED 180 DEGREES TO A VERTICAL ATTITUDE BEFORE GROUND IMPACT. A POST-IMPACT FIRE IMMEDIATELY ENSUED, TOTALLY CONSUMING THE WOOD & FABRIC COMPONENTS OF THE ACFT. AN INVESTIGATION REVEALED THE ELEVATOR TRIM TAB WAS IN THE FULL NOSE-UP POSITION. BELLANCA PERSONNEL REPORTED THAT WITH THE ELEVATOR TRIM IN THAT POSITION & WITH FULL POWER APPLIED, CONTROL FORCES TO REDUCE THE PITCH WOULD BE VERY HIGH & WOULD PROBABLY REQUIRE BOTH HANDS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record SEA85FA084
- Event ID
- 20001214X36313
- Case number
- SEA85FA084
- 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: c034d2341dba0720254ff3874bad7fe6ac50071158adf96b8f469dd9ef349640; retrieved 2026-09-21T05:04:50.986Z.