Gulfstream Aerospace Corp. GV-SP accident near Appleton, Wisconsin, February 14, 2011
On February 14, 2011 at about 7:15 pm local time, a Gulfstream Aerospace Corp. GV-SP, registered N535GA, was substantially damaged in an accident during approach (IFR final approach) near Appleton, Wisconsin (Outagamie County Regional Arpt airport). It was a flight test under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot flying's (PF) decision to land on a shorter-than-recommended runway with a known left hydraulic system failure rather than go around as suggested by the pilot-not-flying, his failure to immediately apply emergency brakes following the detection of the lack of normal brakes, and his attempt to go around late in the landing roll with insufficient runway remaining. Contributing to the accident was the nose landing gear swivel assembly failure, the lack of a hydraulic fuse before this critical failure point, and the design of the swivel using two similar alloys with a propensity to adhere to each other when rubbed together. Also contributing to the accident was the lack of a disciplined cockpit environment.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 14, 2011 · about 7:15 pm local time
- Place
- Appleton, Wisconsin · Outagamie County Regional Arpt · map
- Type
- Accident
- Injuries
- No one was hurt; 3 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Gulfstream Aerospace Corp. GV-SP
- Registration
- N535GA · no longer on the register · serial 5305
- Damage
- Substantial damage
- Flight
- Flight test · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
While the airplane was inside the final approach fix, an amber left side hydraulic quantity low crew alerting system (CAS) message illuminated. The pilot flying (PF) noticed the hydraulic fluid quantity decreasing. Subsequently, an amber left hydraulic system fail CAS message appeared. The pilot not flying (PNF) pulled out the checklist to accomplish the left hydraulic system failure procedures and then suggested a go-around because the landing runway was about 500 feet shorter than the recommended minimum runway length indicated in the checklist. The PF decided to land due to the hydraulic quantity indications, prior autopilot problems, and the airplane's landing configuration. The PNF turned on the auxiliary pump about 500 feet above ground level, and both the PF and PNF thought the auxiliary hydraulic system could support normal spoilers, brakes, and nosewheel steering. The PF selected right thrust reverser aft and began pressing the brakes, but he felt no braking action. He reached for the emergency brakes; however, he did not immediately apply them to slow the airplane because he decided that there was not enough distance remaining to stop the airplane on the runway. Therefore, he attempted to go around with insufficient runway remaining by advancing the throttles to the maximum continuous thrust setting. The PNF did not see the airspeed increase and believed that not enough runway remained to get airborne, so he pulled the throttles back to avoid a runway overrun. The airplane exited the runway and sustained substantial damage. A review of the cockpit voice recorder transcript indicated that, before the emergency, the flight crew did not maintain a disciplined cockpit environment that focused on operationally relevant discussion but instead repeatedly made reference to and discussed objects on the ground and other operationally irrelevant topics. The lack of a sterile cockpit did not promote crew coordination and communication and adherence to procedures, which would have helped mitigate this emergency. A postaccident examination of the airplane revealed that the nose landing gear swivel assembly, which had passed an acceptance test procedure before its installation on the airplane, was seized and bound and had a fracture on its inboard connecting tube, which was the site of the hydraulic fluid leak. The swivel assembly had galling wear scars on the outside diameter of the spool and the inside diameter of the housing; both the spool and housing were made from similar aluminum alloys that have a propensity to gall and adhere to each other when rubbed together. The connecting tube fracture was consistent with a single bending and torsional overload event associated with high opening forces or seizure in the center swivel due to galling wear. The center housing/spool seizure was consistent with a misalignment of the swivel, which led to the binding together of the similar aluminum alloys of the spool and housing. Further examination showed that the nose landing gear hydraulic system did not have a volumetric hydraulic fuse designed to minimize the loss of hydraulic fluid in the event of a line break downstream of such a device.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Sys/Comp malf/fail (non-power) during approach (IFR final approach) defining event
- Runway excursion during landing (landing roll)
The NTSB's findings
- Aircraft › Fluids/misc hardware › Fluids › Hydraulic fluid › Fluid level
- factor Aircraft › Aircraft systems › Hydraulic power system › (general) › Failure
- factor Not determined › Not determined › (general) › (general) › Unknown/Not determined
- cause Personnel issues › Action/decision › Action › Incorrect action selection › Pilot
- cause Personnel issues › Action/decision › Action › Lack of action › Pilot
- cause Personnel issues › Action/decision › Action › Delayed action › Pilot
- factor Personnel issues › Task performance › Communication (personnel) › CRM/MRM techniques › Flight crew
- factor Aircraft › Aircraft systems › Hydraulic power system › (general) › Design
Pilot
- Certificate: airline transport pilot, commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 6,181 hours in all; 555 in this make and model; 82 in the last 90 days; 33 in the last 30 days; 5,115 as pilot in command; 2,535 on instruments
- Last flight review: January 7, 2011
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: left
- Injury: no injuries
Co-pilot
- Certificate: airline transport pilot, commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 4,793 hours in all; 1,176 in this make and model; 90 in the last 90 days; 32 in the last 30 days; 4,105 as pilot in command; 1,141 on instruments
- Last flight review: November 19, 2010
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: rgt
- Injury: no injuries
The aircraft
- Airframe total time: 10 hours
- Maximum gross weight: 91,400 lb
- Seats: 20
- Landing gear: retractable
- Engine 1: Rolls-Royce BR700-710C411 (turbofan); 0 hours total
- Engine 2: Rolls-Royce BR700-710C411 (turbofan); 0 hours total
- Operator: Gulfstream Aerospace Corporation
The flight
- Departed from: ATW Appleton WI at 4:10 pm
- Destination: ATW Appleton WI
- Flight plan: IFR
- Runway 30, 6,501 ft by 150 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 340° at 10 knots
- Visibility: 10 statute miles
- Sky: a few clouds at 3,500 ft
- Temperature: 36°F (2°C), dew point 19°F (-7°C)
- Altimeter: 30.12 inHg
- Observation at 7:27 pm from ATW
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
