FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR15IA046 · Embraer EMB-505

23 Nov 2014 · Palm Springs, CA, United States

Embraer EMB-505 · Incident: system/component malfunction/failure (non-power) during initial climb

From Palm Springs International Airport (PSP) to Calgary / Springbank Airport (CYBW)

Report a problem

Event

NTSB case
WPR15IA046
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
Incident
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

Embraer EMB-505

Aircraft type
Embraer EMB-505
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
C-GJOL
Operator
Unknown
Onboard fatalities
Unknown
Route
From Palm Springs International Airport (PSP), Palm Springs, CATo Calgary / Springbank Airport (CYBW), Springbank
Aircraft age
About 2 years (built 2012)
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
Initial climb
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
System/component malfunction/failure (non-power)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Aircraft › Aircraft systems
  • Not determined › Not determined

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

NTSB narrative

The airline transport pilot was preparing to take off for a personal cross-country flight. He reported that the preflight preparations were normal, including the removal of the rudder gust lock pin. He stated that the taxi out for takeoff was normal but that he "detected an abnormal 'feel' to the rudders." He added that all of the turns to the runway were right turns and that he "easily executed" the turns. Following rotation on takeoff, the pilot noticed a significant right yaw and roll, which he initially countered with left aileron. As the airplane continued to climb, the airplane's flight was uncoordinated, and the pilot had to continuously apply left rudder to counter the right yaw; he also attempted to apply left yaw trim, but neither action resolved the issue. At this time, the pilot advised air traffic control (ATC) that he needed to return to the departure airport, and ATC cleared the pilot for a visual approach. The pilot landed the airplane; only minor damage to the left wing tip was incurred as the pilot tried to unsuccessfully correct (with the right rudder and aileron) a drift to the right after landing.

The initial examination of the airplane revealed that the rudder gust lock had failed in the locked position. Upon further examination, it was determined that the gust lock actuator had likely begun to retract as commanded by the pilot when he removed the rudder gust lock pin during the preflight/startup checks. However, the solenoid located within the gust lock actuator failed, which resulted in the pin no longer being held in the retracted position. Once the pin released from its retracted position, it engaged the ball nut, which then stopped the rotation of the actuator shaft. The failure occurred at a time when the gust lock bellcrank had not fully disengaged from the rudder quadrant, which likely resulted in the rudder being locked throughout the taxi, takeoff, climb, descent, approach and landing, and landing roll segments of the flight.

Although it is possible that a momentary power interruption could have caused the solenoid pin to release, which would have then resulted in the pin moving to the extended position and interfering with the ball nut, no conclusive evidence was found during the investigation that supported this possibility. The reason for the failure of the gust lock actuator solenoid could not be determined.

Probable cause

The failure of the gust lock actuator solenoid for reasons that could not be determined because postaccident examination of the rudder gust lock system revealed no mechanical malfunctions or failures that would have precluded normal operation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR15IA046
Event ID
20141123X61400
Case number
WPR15IA046
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: 56d5247a657b27a171291209c50046afddac4d1b6f0ad01b04b87667cc305ab7; retrieved 2026-09-16T01:56:37.581Z.