OpenAirDocs.org

20131018021029I

Incident · Minor damage
Open the Markdown

FAA incident report · Bellanca 17-30A · Sarasota, FL · October 18, 2013

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
October 18, 2013 · 07:56 local
Place
Sarasota, FL
Phase of flight
Takeoff: Rotation
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N122RH
Reported as
Bellanca 17-30A
Reported engine
Continental IO-520 series
People aboard
2
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Private pilot
Pilot’s flight hours
400 total60 in this make and model10 in the last 90 days
N122RHRegistered now · Bellanca 17-30AS/N 93-301017 · Built 1993Airframe modelBellanca 17-30AEngine modelContinental IO-520 seriesReciprocating

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

Interviewedprivacy data omittedoperator of this aircraft and he stated that on takeoff, the aircraft settled back down then immediately pitched up and became uncontrollable, the aircraft began porpoising and the pilot cut power to land.

The aircraft struck the runway at a nose low angle, breaking the nose gear and contacting the propeller on the runway.

The pilot stated that engine power was normal.

The pilot also stated that on all previous flights, this aircraft had a tendency to settle immediately after lift off.

Inspection revealed that weight and balance was not a factor.

All flight control cables appeared to be properly run and on their respective pulleys.

Flight control and trim continuity was verified with no anomalies.

Based on the interview with the pilot, it is suspected that there may be a malfunction with the airspeed indication causing the aircraft to be flown off too early, which in turn is causing the aircraft to settle.

If this is the case then the incident flight loss of control can be attributed to a stall.

As the FAA filed it

INTERVIEWED^PRIVACY DATA OMITTED^OPERATOR OF THIS AIRCRAFT AND HE STATED THAT ON TAKEOFF, THE AIRCRAFT SETTLED BACK DOWN THEN IMMEDIATELY PITCHED UP AND BECAME UNCONTROLLABLE, THE AIRCRAFT BEGAN PORPOISING AND THE PILOT CUT POWER TO LAND.

THE AIRCRAFT STRUCK THE RUNWAY AT A NOSE LOW ANGLE, BREAKING THE NOSE GEAR AND CONTACTING THE PROPELLER ON THE RUNWAY.

THE PILOT STATED THAT ENGINE POWER WAS NORMAL.

THE PILOT ALSO STATED THAT ON ALL PREVIOUS FLIGHTS, THIS AIRCRAFT HAD A TENDENCY TO SETTLE IMMEDIATELY AFTER LIFT OFF.

INSPECTION REVEALED THAT WEIGHT AND BALANCE WAS NOT A FACTOR.

ALL FLIGHT CONTROL CABLES APPEARED TO BE PROPERLY RUN AND ON THEIR RESPECTIVE PULLEYS.

FLIGHT CONTROL AND TRIM CONTINUITY WAS VERIFIED WITH NO ANOMALIES.

BASED ON THE INTERVIEW WITH THE PILOT, IT IS SUSPECTED THAT THERE MAY BE A MALFUNCTION WITH THE AIRSPEED INDICATION CAUSING THE AIRCRAFT TO BE FLOWN OFF TOO EARLY, WHICH IN TURN IS CAUSING THE AIRCRAFT TO SETTLE.

IF THIS IS THE CASE THEN THE INCIDENT FLIGHT LOSS OF CONTROL CAN BE ATTRIBUTED TO A STALL.