Avantair Piaggio P180 accident
Piaggio P180 · Accident: flight control system malfunction/failure during takeoff
From San Diego International Airport (KSAN) to Henderson Executive Airport (KHND)
Event
- NTSB case
- WPR12FA332
- 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
- Charter & commuter
- 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
Piaggio P180
- Aircraft type
- Piaggio P180
- 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
- N146SL
- Operator
- Avantair
- Onboard fatalities
- Unknown
- Route
- From San Diego International Airport (KSAN), San Diego, CATo Henderson Executive Airport (KHND), Henderson, NV
- Aircraft age
- About 8 years (built 2004)
- 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 135: Air Taxi & Commuter
- 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
- Takeoff
- 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
- Flight control system malfunction/failure
- 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 systems
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The twin-engine airplane departed 23 minutes behind schedule to pick up passengers at an intermediate airport. During the takeoff roll, the left elevator departed the airplane and was found off the side of the runway 3 days later. The crew arrived at the intermediate airport and quickly boarded the two waiting passengers. They did not perform an adequate preflight inspection and departed about 5 minutes behind schedule. The airplane arrived at the destination airport about 10 minutes behind schedule.
Upon postflight examination by the crew, the left elevator was observed missing from the tail's horizontal stabilizer. An examination of the attachment nuts on the hinges of the right elevator found that they were finger tight. Examination of the hinge fittings on the left elevator and horizontal stabilizer revealed no mechanical damage or deformation to any of the components. Review of airplane maintenance records showed that an airworthiness directive (AD) had been complied with 54 days earlier, which involved both elevators being removed and then reinstalled.
Materials laboratory examination of one of the right elevator attachment hardware bolt-nut combinations revealed that the self-locking nut exhibited run-on torque values well below the acceptable minimum torque. Based on the finger tight condition of the right elevator attachment hardware and the lack of any mechanical damage to the hinge fittings of the left elevator and stabilizer hinge structure, it is likely that all four sets of attachment hardware for both elevators were not properly torqued during the AD maintenance 54 days earlier. Additionally, 26 days before the event, a phase inspection was completed during which the elevator should have been visually inspected and functionally checked. The airplane had flown 158.9 hours with loose elevator attachment hardware before the two sets of bolts on the left elevator had completely worked their way out of the hinges, and the elevator departed the airplane.
The cockpit voice recorder revealed that the flight crew had experienced unusual pitch control responses during each of the departures and landings. The flight crew could have identified the missing elevator during a preflight inspection at the intermediate airport, yet they decided to continue the flight despite the pitch control problems experienced during the takeoffs and landing.
Probable cause
The failure of maintenance personnel to properly torque the elevator attachment hardware in accordance with the maintenance manual, which led to the detachment of the elevator. Contributing to the accident were maintenance personnel's failure to identify the loose attachment hardware during a scheduled inspection, the flight crew's decision to continue the flight after identifying a flight control problem, and the flight crew's failure to perform an adequate preflight inspection at the intermediate airport.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR12FA332
- Event ID
- 20120730X73433
- Case number
- WPR12FA332
- 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: 96b9d2d44ba69ca2cb84730cfba0844e8ee1781f68a3e61dcaf9f0847f4a69cb; retrieved 2026-09-15T19:07:06.841Z.