FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA22LA115 · Pilatus Aircraft Ltd PC-12/47E

2 Feb 2022 · Ronkonkoma, NY, United States

ExcelAire Pilatus Aircraft Ltd PC-12/47E · Accident while standing

From an unrecorded airport to Republic Airport (FRG)

Report a problem

Event

NTSB case
ERA22LA115
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
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

Pilatus Aircraft Ltd PC-12/47E

Aircraft type
Pilatus PC-12
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
N357JK
Operator
ExcelAire
Onboard fatalities
Unknown
Route
From not recordedTo Republic Airport (FRG), Farmingdale, NY
Aircraft age
About 9 years (built 2013)
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
Standing · engine(s) start-up
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
Miscellaneous/other
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 power plant
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot and a pilot-rated passenger were starting the engine before a positioning flight. The airplane’s cockpit voice recorder captured some checklist usage; however, there was no comment for the position of the power control lever (PCL) in the “Cockpit” checklist. Although the checklist specified and the pilot reported that the PCL was in the idle position at engine start, based on the flight data recorder (FDR) data, it was not in the idle position at any time during the engine start or accident sequence. After the engine was started with the parking brake engaged and the pilot’s application of normal toe brakes, the airplane accelerated on the ramp to a maximum speed of 26 knots and briefly attained a maximum propeller speed of 1,870 rpm, which was likely due to the cold engine oil temperature, but well within rpm and time limits. The pilot was unable to stop the airplane on the ramp, which likely contained ice, or to move the condition lever (CL) to stop the engine, and the airplane impacted a parked, unoccupied airplane, resulting in substantial damage.

Although cockpit rigging checks of the PCL and CL showed out-of-tolerance conditions, rigging checks at the engine for those controls and for the cut-off guard of the CL in the cockpit revealed no evidence of preimpact failure or malfunction that would have precluded a normal engine start. There were no discrepancies with the fuel control unit that would have caused the engine acceleration issue at engine start, and there were no discrepancies with the parking brake or the left brake. Although testing of the right brake was not performed due to separation of the right wing, there was no evidence of preimpact failure or malfunction of the brakes or parking brake that contributed to the collision. While there was no flat-spotting of either main landing gear tire, alternating skid marks on the ramp were likely due to the ice on the ramp.

Recorded data from a previous, uneventful engine start performed by the accident pilot with the PCL in the idle position revealed normal engine parameters. Testing of an exemplar airplane with the PCL in the correct position at engine start (idle) and the CL in either ground or flight idle positions during engine start revealed little forward movement with no brakes applied.

The PCL was found in a forward position following the accident. Although the exact position of the PCL at engine start could not be determined from the FDR information, based on the maximum engine and propeller parameters recorded by the FDR, and the speed the airplane reached before the collision, it is likely that the PCL was nearly fully advanced during the engine start. Had the pilot performed a flow check then reviewed the checklists for any missed items or engaged the passenger to perform challenge-and-response to the entire checklist, the incorrect position of the PCL could have been detected and corrected before engine start.

Though the pilot reported being unable to secure the CL while accelerating and approaching the parked airplane, there were no reported discrepancies with the cut-off guard, or of the CL during postaccident operational testing. Therefore, the pilot’s unsuccessful attempt to secure the CL were likely due to errors made while multitasking when presented with an unexpected situation (airplane acceleration during engine start and being unable to stop the airplane) while fast approaching a parked airplane.

Probable cause

The pilot’s failure to properly position the power control lever before starting the engine as required per the checklist. Contributing to the accident were the ice on the ramp and the pilot’s failure to secure the engine using the condition lever.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA22LA115
Event ID
20220202104590
Case number
ERA22LA115
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, cause areas. 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: 2b76c7ab3c312780316ceefa9bad1798ddb15b8b3c3e04beb5396704156c57cc; retrieved 2026-09-16T14:55:55.363Z.