San Jose - Sedona
Flight / Schedule
San Jose - Sedona
Aircraft
Embraer EMB-500 Phenom 100Registration
N224MD
MSN
500-00057
Year of Manufacture
2009
Operator
JetSuiteDate
May 25, 2011 at 03:50 PM
Type
CRASHFlight Type
Charter/Taxi (Non Scheduled Revenue Flight)
Flight Phase
Landing (descent or approach)
Crash Site
Airport (less than 10 km from airport)
Crash Location
Sedona Arizona
Region
North America • United States of America
Coordinates
34.8689°, -111.7614°
Crash Cause
Human factor
Narrative Report
On May 25, 2011 at 03:50 PM, San Jose - Sedona experienced a crash involving Embraer EMB-500 Phenom 100, operated by JetSuite, with the event recorded near Sedona Arizona.
The flight was categorized as charter/taxi (non scheduled revenue flight) and the reported phase was landing (descent or approach) at a airport (less than 10 km from airport) crash site.
5 people were known to be on board, 0 fatalities were recorded, 5 survivors were identified or estimated. This corresponds to an estimated fatality rate of 0.0%.
Crew on board: 2, crew fatalities: 0, passengers on board: 3, passenger fatalities: 0, other fatalities: 0.
The listed crash cause is human factor. Following an uneventful flight, the flight crew briefed the arrival to the destination airport and set the calculated landing speeds. The captain and the first officer reported that during final approach, it felt like the airplane was “pushed up” as the wind shifted to a tailwind or updraft before landing near the runway number markings. Upon touchdown, the captain applied the brakes and thought that the initial braking was effective; however, he noticed the airplane was not slowing down. The captain applied maximum braking, and the airplane began to veer to the right; he was able to correct back to the runway centerline, but the airplane subsequently exited the departure end of the runway and traveled down a steep embankment. A pilot-rated passenger reported that throughout the approach to landing, he thought the airplane was high and thought that the excessive altitude continued through and into the base-to-final turn. He added that the bank angle of this turn seemed greater than 45 degrees. Recorded communication from the cockpit voice and data recorder (CVDR) revealed that during the approach to landing, the flight crew performed the landing checks, and the captain noted difficulty judging the approach. About 1 minute later, the recording revealed that the ground warning proximity system reported “five hundred” followed by a “sink rate, pull up” alert about 16 seconds later. Data from the CVDR revealed that about 23 seconds before weight-on-wheels was recorded, the airplane was at an indicated airspeed of about 124 knots and descending. The data showed that this approximate airspeed was maintained until about 3 seconds before weight-on-wheels. The recorded data further showed that the approach speed was set to 120 knots, and the landing reference speed (vREF) was set to 97 knots. Using the reported airplane configuration and the 3.5-knot headwind that was reported at the time of the approach and landing, calculations indicate that the vREF speed should have been about 101 knots indicated airspeed, which would have required a landing distance of about 3,112 feet. Utilizing the same airplane configuration and wind condition with the flight’s reported 124 knot indicated airspeed just before touchdown, the landing distance was calculated to be about 5,624 feet. The intended runway for landing was 5,132-feet long with a 1.9 percent downward slope gradient, and a 123-foot long overrun area. A postaccident examination of the airplane, including the braking system, revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. The pilot misjudged the airplane’s speed during the final approach, which resulted in runway overrun.
Aircraft reference details include registration N224MD, MSN 500-00057, year of manufacture 2009.
Geospatial coordinates for this crash are approximately 34.8689°, -111.7614°.
Fatalities
Total
0
Crew
0
Passengers
0
Other
0
Crash Summary
Following an uneventful flight, the flight crew briefed the arrival to the destination airport and set the calculated landing speeds. The captain and the first officer reported that during final approach, it felt like the airplane was “pushed up” as the wind shifted to a tailwind or updraft before landing near the runway number markings. Upon touchdown, the captain applied the brakes and thought that the initial braking was effective; however, he noticed the airplane was not slowing down. The captain applied maximum braking, and the airplane began to veer to the right; he was able to correct back to the runway centerline, but the airplane subsequently exited the departure end of the runway and traveled down a steep embankment. A pilot-rated passenger reported that throughout the approach to landing, he thought the airplane was high and thought that the excessive altitude continued through and into the base-to-final turn. He added that the bank angle of this turn seemed greater than 45 degrees. Recorded communication from the cockpit voice and data recorder (CVDR) revealed that during the approach to landing, the flight crew performed the landing checks, and the captain noted difficulty judging the approach. About 1 minute later, the recording revealed that the ground warning proximity system reported “five hundred” followed by a “sink rate, pull up” alert about 16 seconds later. Data from the CVDR revealed that about 23 seconds before weight-on-wheels was recorded, the airplane was at an indicated airspeed of about 124 knots and descending. The data showed that this approximate airspeed was maintained until about 3 seconds before weight-on-wheels. The recorded data further showed that the approach speed was set to 120 knots, and the landing reference speed (vREF) was set to 97 knots. Using the reported airplane configuration and the 3.5-knot headwind that was reported at the time of the approach and landing, calculations indicate that the vREF speed should have been about 101 knots indicated airspeed, which would have required a landing distance of about 3,112 feet. Utilizing the same airplane configuration and wind condition with the flight’s reported 124 knot indicated airspeed just before touchdown, the landing distance was calculated to be about 5,624 feet. The intended runway for landing was 5,132-feet long with a 1.9 percent downward slope gradient, and a 123-foot long overrun area. A postaccident examination of the airplane, including the braking system, revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. The pilot misjudged the airplane’s speed during the final approach, which resulted in runway overrun.
Cause: Human factor
Occupants & Outcome
Crew On Board
2
Passengers On Board
3
Estimated Survivors
5
Fatality Rate
0.0%
Known people on board: 5
Operational Details
Schedule / Flight
San Jose - Sedona
Operator
JetSuiteFlight Type
Charter/Taxi (Non Scheduled Revenue Flight)
Flight Phase
Landing (descent or approach)
Crash Site
Airport (less than 10 km from airport)
Region / Country
North America • United States of America
Aircraft Details
Similar Plane Crashes
United States Signal Corps - USSC
De Havilland DH.4
The single engine airplane departed Dayton-McCook Field for a local test flight. Shortly after takeoff, the aircraft stalled and crashed, killing both occupants. Crew: Maj Oscar Brindley, Lt Col Henry Damm.
United States Signal Corps - USSC
De Havilland DH.4
Lt. Frank Stuart Patterson, son and nephew of the co-founders of National Cash Register, is killed in the crash of his DH.4M, AS-32098, at Wilbur Wright Field during a flight test of a new mechanism for synchronizing machine gun and propeller, when a tie rod breaks during a dive from 15,000 feet (4,600 m), causing the wings to separate from the aircraft. Wishing to recognize the contributions of the Patterson family (owners of NCR) the area of Wright Field east of Huffman Dam (including Wilbur Wright Field, Fairfield Air Depot, and the Huffman Prairie) is renamed Patterson Field on 6 July 1931, in honor of Lt. Patterson.
United States Signal Corps - USSC
De Havilland DH.4
The aircraft crashed in unknown circumstances.
United States Signal Corps - USSC
De Havilland DH.4
The crew was completing a training mission. At an altitude of about 4,000 feet, the aircraft entered a spin and crashed in an open field near Everman-Barron Field Airport. A crew was killed and the second occupants was injured. The aircraft was destroyed.
U.S. Air Mail Service
De Havilland DH.4
Crashed following an engine failure. Pilot fate unknown.
United States Signal Corps - USSC
De Havilland DH.4
The accident occurred in unknown circumstances.
