EMBRAER-EMPRESA BRASILEIRA DE EMB-500 near Sedona, AZ — 2011-05-25
- Date
- 2011-05-25
- Location
- Sedona, AZ, USA
- Airport
- SEZ
- Aircraft
- EMBRAER-EMPRESA BRASILEIRA DE EMB-500
- Registration
- N224MD
- Category
- Airplane
- Highest injury
- Serious
- Fatalities
- 0
- Phase of flight
- Landing
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.
NTSB narrative
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.
Analysis
- Primary failure mode
- Controlled flight into terrain
- First missed decision gate
- Initiating a go-around when the approach was high and unstable.
NTSB coding
Evidence available
- CVR
- FDR / data
- Photos
- 29 docket documents
Docket documents29
- Cockpit Voice Recorder 12 - Specialist's Factual Reportcvr
- Flight Data Recorder and Other Devices 10 - Attachment 1 - Tabular Data - CVDR (CSV Format)fdr
- Flight Data Recorder and Other Devices 10 - Attachment 2 - Tabular Data - GDU 1440 Maintenance Computer (CSV Format)fdr
- Flight Data Recorder and Other Devices 10 - Specialist's Factual Reportfdr
- Aircraft Performance 13form
- Embraer Performance Calculationsform
- Captain - Statementinterview
- First Officer - Statementinterview
- Passenger - Statementinterview
- Statement of Party Representatives to NTSB Investigation - JetSuiteinterview
- Statement of Party Representatives to NTSB Investigation - Meggittinterview
- Statement of Party Representatives to NTSB Investigation - PVIinterview
- Witness Statementinterview
- BCU Exam Summaryother
- Captain - 72 Hour Rest Historyother
- Captain - Record of Conversationother
- First Officer - 72 Hour Rest Historyother
- First Officer - Record of Conversationother
- JetSuite Standard Operating Procedure for Before Landingother
- Passenger - Record of Conversationother
- Portions of the Airplane Flight Manualother
- Summary of NTSB Accident Site and Aircraft Examinationother
- Photo 1: View of the tire marks on runway 21 near alpha 6.photos
- Photo 2: View of the tire marks in the runway overrun area of runway 21.photos
- Photo 3: View of the wreckage debris path downslope of runway 21.photos
- Photo 4: View of the main wreckage.photos
- Photo 5: View of the main wreckage.photos
- Photo 6: View of the main wreckage.photos
- Meteorology 5 - Weather Study Report of Group Chairmanreport
Related mishaps
- JEREMY PRICE SMITH SUPER CUB
2026-07-19 · Allisonia, VA
- CESSNA 172S
2026-06-17 · DEATH VALLEY, CA
- PIPER PA 31P 350
2026-04-17 · Ardmore, OK
- CESSNA 180K
2026-03-27 · Beloit, KS
- CESSNA T210
2026-03-11 · Upland, CA
- FRANKEWICH WALTER S-21 OUTBOUND
2026-01-19 · Madisonville, TN