Accident Embraer EMB-500 Phenom 100 N224MD,

ASN Wikibase Occurrence # 321113

Date:	Wednesday 25 May 2011
Time:	15:52
Type:	Embraer EMB-500 Phenom 100
Owner/operator:	JetSuite
Registration:	N224MD
MSN:	50000057
Year of manufacture:	2009
Total airframe hrs:	1052 hours
Engine model:	Pratt & Whitney Canada PW617F-E
Fatalities:	Fatalities: 0 / Occupants: 5
Aircraft damage:	Substantial, written off
Category:	Accident
Location:	Sedona Airport, AZ (SDX) - United States of America
Phase:	Landing
Nature:	Passenger - Non-Scheduled/charter/Air Taxi
Departure airport:	San Jose-Norman Y. Mineta International Airport (SJC/KSJC)
Destination airport:	Sedona Airport, AZ (SDX/KSEZ)
Investigating agency:	NTSB
Confidence Rating:	Accident investigation report completed and information captured

Narrative:
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 flights 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: "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: