GULFSTREAM G150 near Key West, FL — 2011-10-31
- Date
- 2011-10-31
- Location
- Key West, FL, USA
- Airport
- EYW
- Aircraft
- GULFSTREAM G150
- Registration
- N480JJ
- Category
- Airplane
- Highest injury
- Serious
- Fatalities
- 0
- Phase of flight
- Landing
Probable cause
The pilot in command's failure to follow the normal landing procedures (placing engines into reverse thrust first and then brake), his delayed decision to continue the landing or go-around, and the flight crew's failure to follow emergency procedures once a perceived loss of brakes occurred. Contributing to the seriousness of the passenger's injury was the improper securing of the passenger seat by maintenance personnel.
Contributing factors
Contributing to the seriousness of the passenger's injury was the improper securing of the passenger seat by maintenance personnel.
NTSB narrative
The airplane was approaching the destination airport in night visual meteorological conditions. After losing sight of the runway once and going around, they continued the approach, even though the pilot in command (PIC) stated that he thought they were going to land long. The PIC stated that the main landing gear touched down near the 1,000-foot marker of the 4,801-foot-long runway, about the landing reference speed (Vref) of 120 knots. The PIC stated that he then applied the brakes but thought they were not working; he had not yet activated the thrust reversers. He alerted the second in command (SIC), who also depressed the brake pedals with no apparent results. The PIC suggested a go-around, but the SIC responded that it was too late. The airplane subsequently traveled off the end of the runway, struck a gravel berm, and came to rest about 816 feet beyond the end of the runway. During the impact, one of the passenger seats dislodged from its seat track and was found on the cabin floor, with the passenger still in it. Review of cockpit voice recorder, video, and performance data revealed that the main landing gear touched down at Vref and about 1,650 feet beyond the approach end of the runway. The nosegear then touched down 2.4 seconds later and about 2,120 feet beyond the approach end of the runway, with about 2,680 feet of runway remaining. Digital electronic engine control data revealed that about 8 seconds after weight-on-wheels, the power levers were advanced from the idle position to the takeoff position. The power levers were then returned to the idle position 6 seconds later. The power levers were moved to the reverse thrust position 8 seconds after that and remained in that position for the duration of the accident sequence; both thrust reversers deployed when commanded. Examination and testing of the airplane systems did not reveal any evidence of preimpact mechanical malfunctions with the wheels brakes or any other systems. Although armed, the airbrakes did not deploy upon touchdown; the data available was inconclusive to determine what position the throttles were in at touchdown and why the airbrakes did not deploy. It is likely that the pilots did not detect the wheel braking because its effect was less than expected with the airplane at full power and with the airbrakes stowed. Landing distance data revealed that the airplane required about 2,551 feet to stop at its given weight in the given weather conditions. With a runway distance of 2,680 feet remaining, the airplane could have stopped or gone around uneventfully with appropriate use of all deceleration devices. The landing procedure stated to activate the thrust reversers after nosewheel touchdown and then apply the brakes, as necessary; however, the PIC only applied the brakes. Further, no callouts were made to verify ground spoiler or reverse thrust deployment. The PIC then stated that he was going to go around, but the SIC said it was too late, so the thrust levers were brought back to idle and the reversers were deployed. The PIC's delayed decision to stop or go around resulted in about a 22-second delay in thrust reverser activation, which resulted in the runway overrun. Additionally, the procedure for a (perceived) failed brake system would have been to activate the emergency brake, which neither pilot did. Examination of the seats revealed that a forward-facing seat was installed in the aft-facing position and an aft-facing seat was installed in the forward-facing position. Additionally, the ejected seat's shear plungers were found in the raised position. Had the seat been installed correctly, the plungers would have been in the lowered position, in the seat track. The improper installation most likely resulted in the passenger’s seat separating from the seat track and exacerbating his injuries.
Analysis
- Primary failure mode
- Mechanical failure
- First missed decision gate
- Utilizing emergency brake system after realizing brakes were not working.
NTSB coding
Evidence available
- CVR
- Video
- FDR / data
- Photos
- 51 docket documents
Docket documentsshowing 50 of 51
- Cockpit Voice Recorder 12 - Factual Report of Group Chairmancvr
- Aircraft Performance 13 - Studyform
- Evidence Control Formsform
- Human Performance 14 - Attachment 1: Interview Summariesform
- Human Performance 14 - Factual Report of Group Chairmanform
- Non-Volatile Memory Devices - Attachment 1 - Tabular Data - (CSV Format)form
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1form
- Release of Aircraft Wreckage, NTSB Form 6120.15form
- Additional Flight Crew Follow Up Statementinterview
- Controller Statementinterview
- Interview Summaryinterview
- Interview Summary - EYW Airport Managerinterview
- Statement of Party Representatives to NTSB Investigationinterview
- Extract Aircraft Logbooksother
- Extract G150 Quick Reference Handbook, Brake Proceduresother
- Extract Hendrick G150 Standard Operating Proceduresother
- Extract Hendrick Motorsport Flight Operations manualother
- Flight Planother
- Fuel Receiptother
- G150 Cockpit Card/Checklistother
- Key West Airport Diagramother
- Key West Instrument Approach RNAV (GPS) Runway 27other
- Key West Surface Weather Observationother
- Landing Distance Data, N480JJother
- Sun and Moon Dataother
- Survival Factors 6 - Attachment 1other
- Survival Factors 6 - Attachment 2other
- Survival Factors 6 - Attachment 3other
- Survival Factors 6 - Attachment 4other
- Survival Factors 6 - Attachment 5other
- Survival Factors 6 - Attachment 6other
- Survival Factors 6 - Attachment 7other
- Computed Tomography Specialist's Factual Report (with 10 embedded images)photos
- Photo 1 High altitude vertical view of EYW Airport.. Source Key West Airport Authorityphotos
- Photo 10 Front view of airplane during recovery. Photo NTSBphotos
- Photo 11 Left side view of airplane during recovery. Photo NTSBphotos
- Photo 12 Emergency Brake Handle as Found After The Accident.. NTSB Photophotos
- Photo 13 Cockpit Center Pedestal as Found After The Accident. NTSB Photophotos
- Photo 2 View of departure end of runway. Photo NTSBphotos
- Photo 3 View looking back at initial overrun. Photo NTSBphotos
- Photo 4 View of overrun with dirt road in background. Photo NTSBphotos
- Photo 5 Left rear side view of airplane at rest. Photo FAAphotos
- Photo 6 Left forwrard side view of airplane. Photo NTSBphotos
- Photo 7 Right side view of airplane. Photo NTSBphotos
- Photo 8 Rear view of airplane at rest. Photo NTSBphotos
- Photo 9 Left front view of cockpit area during recovery. Photo NTSBphotos
- Factual Report of On Scene Cabin Documentationreport
- Non-Volatile Memory Devices - Specialist's Factual Reportreport
- Survival Factors 6 - Factual Report of Group Chairmanreport
- Systems 9 - Factual 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