ASN Aircraft accident Embraer EMB-500 Phenom 100 N224MD Sedona Airport, AZ (SDX)
ASN logo

Status:Accident investigation report completed and information captured
Date:Wednesday 25 May 2011
Type:Silhouette image of generic E50P model; specific model in this crash may look slightly different
Embraer EMB-500 Phenom 100
Registration: N224MD
MSN: 50000057
First flight: 2009
Total airframe hrs:1052
Engines: 2 Pratt & Whitney Canada PW617F-E
Crew:Fatalities: 0 / Occupants: 2
Passengers:Fatalities: 0 / Occupants: 3
Total:Fatalities: 0 / Occupants: 5
Aircraft damage: Substantial
Aircraft fate: Written off (damaged beyond repair)
Location:Sedona Airport, AZ (SDX) (   United States of America)
Phase: Landing (LDG)
Nature:Domestic Non Scheduled Passenger
Departure airport:San Jose-Norman Y. Mineta International Airport (SJC/KSJC), United States of America
Destination airport:Sedona Airport, AZ (SDX/KSEZ), United States of America
An Embraer Phenom 100 corporate jet, N224MD, sustained substantial damage during a runway overrun during landing at the Sedona Airport (SEZ), Arizona. The captain, who was the flying pilot, and two of the three passengers were not injured. The first officer and one passenger sustained serious injuries. The airplane was registered to a private individual and operated by JetSuite. Visual meteorological conditions prevailed and an instrument flight rules (IFR) flight plan was filed. The flight originated from San Jose, California, about 14:20 hours local time.
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.

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.

Probable Cause:

PROBABLE CAUSE: "The pilots’ unstabilized approach and excessive airspeed during approach, which resulted in an insufficient landing distance to stop the airplane before overrunning the runway."

Accident investigation:

Investigating agency: NTSB
Status: Investigation completed
Duration: 2 years and 3 months
Accident number: WPR11FA236
Download report: Summary report

Landing after unstabilized approach
Runway excursion (overrun)



photo of Embraer-EMB-500-Phenom-100-N224MD
accident date: 25-05-2011
type: Embraer EMB-500 Phenom 100
registration: N224MD
photo of Embraer-EMB-500-Phenom-100-N224MD
accident date: 25-05-2011
type: Embraer EMB-500 Phenom 100
registration: N224MD
photo of Embraer-EMB-500-Phenom-100-N224MD
accident date: 25-05-2011
type: Embraer EMB-500 Phenom 100
registration: N224MD
photo of Embraer-EMB-500-Phenom-100-N224MD
accident date: 25-05-2011
type: Embraer EMB-500 Phenom 100
registration: N224MD

This map shows the airport of departure and the intended destination of the flight. The line between the airports does not display the exact flight path.
Distance from San Jose-Norman Y. Mineta International Airport to Sedona Airport, AZ as the crow flies is 946 km (591 miles).

This information is not presented as the Flight Safety Foundation or the Aviation Safety Network’s opinion as to the cause of the accident. It is preliminary and is based on the facts as they are known at this time.
languages: languages


The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2023 Flight Safety Foundation

1920 Ballenger Av., 4th Fl.
Alexandria, Virginia 22314