Iai GULFSTREAM200 incident near Jamestown, New York, June 20, 2013
On June 20, 2013 at about 6:10 pm local time, a Iai GULFSTREAM200, registered N500AG, suffered minor damage in an incident during landing (landing roll) near Jamestown, New York (Chataqua County / Jamestown airport). It was an instructional flight under general aviation rules (Part 91). No one was hurt; 5 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilots’ failure to effectively use the airplane's primary (brakes), secondary (thrust reversers), and emergency braking systems to decelerate the airplane, which resulted in a runway excursion. Contributing to the accident was the pilots’ failure to conduct a go-around maneuver upon recognizing that the airplane had excessive airspeed while on final approach to the runway.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 20, 2013 · about 6:10 pm local time
- Place
- Jamestown, New York · Chataqua County / Jamestown · map
- Type
- Incident
- Injuries
- No one was hurt; 5 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Iai GULFSTREAM200
- Registration
- N500AG · registry record · serial 158
- Damage
- Minor damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot flying (PF) and the pilot monitoring (PM) were completing an airman competency check under the observation of a Federal Aviation Administration inspector. Following an uneventful flight, the pilots configured the turbofan-powered, transport-category airplane for landing on the 5,299-ft-long, dry runway. A review of the cockpit recorder (CVR) transcript revealed that, during the practice instrument landing system approach, the PM warned the PF that the airplane was approaching the runway at an airspeed 15 knots higher than its specified approach speed (Vref) as it descended to within 100 ft of the ground. The PM also warned the PF not to allow the airplane's airspeed to increase because the runway was "short." The airplane subsequently touched down within the airplane's touchdown zone about 1,000 ft beyond the runway threshold. The PM reported that he attempted to slow the airplane by applying the brakes and deploying the thrust reversers, but the airplane continued off the departure end of the runway and came to rest about 40 ft beyond its pavement. The runway distance required for the landing was calculated using the airplane manufacturer's Airplane Flight Manual. It was determined that, given the airplane's loading and configuration and the weather and runway conditions, sufficient runway was available for the landing. The landing distance calculations were predicated on the airplane crossing the runway threshold at Vref and did not account for the use of reverse thrust during the landing roll. Postincident examination of the airplane's braking and thrust reverser systems revealed no evidence of any mechanical anomalies that would have precluded normal operation. Although the PF reported in postincident statements that the braking action during the landing was "nil," a review of the CVR transcript showed that neither of the pilots mentioned poor braking performance during the landing roll nor did they attempt to activate the emergency braking system. Additionally, the operator's chief pilot, who had been seated in the cabin during the flight, reported that the braking system cycled several times during the landing roll and that, although the reverse thrust system appeared to activate, he did not "feel or hear" a pronounced application of reverse thrust. Although the electronic engine control system recorded a limited set of parametric data during the landing, airspeed was not a recorded parameter. Analysis of the recorded data revealed that, about 3 seconds after touchdown, the throttle lever angles (TLA) were positioned for deployment of the thrust reversers and that the thrust reversers subsequently deployed; however, the TLAs remained at an idle-thrust position. The TLAs did not increase to the maximum reverse thrust position until about 17 seconds later, at which time, both engines increased power for about 8 seconds. Although the use of reverse thrust was not required for the landing, nor was the airplane's computed landing distance reflective of the use of reverse thrust, the PF's apparent delayed application of reverse thrust suggested that he may not have used maximum effort in his attempts to decelerate the airplane during the landing roll even after the outcome was in doubt. Additionally, although an exact account of the airplane's airspeed was not available for postincident analysis, the PM's airspeed callouts suggested that the airplane's airspeed while on final approach to the runway, and potentially throughout the touchdown, increased the total required landing distance. If the pilots had recognized this earlier in the approach, they could have conducted a go-around and avoided the possibility of a runway overrun. Alternatively, upon realizing that the airplane was not decelerating as desired, the pilots could have used all available means to slow the airplane during the landing roll, including the timely and complete activation of the airplane's thrust reversers, and if necessary, activation of the emergency braking system.
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
- Runway excursion during landing (landing roll) defining event
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Aircraft capability › Landing distance › Not attained/maintained
- cause Aircraft › Aircraft systems › Landing gear system › Brake › Incorrect use/operation
- factor Personnel issues › Action/decision › Info processing/decision › Understanding/comprehension › Flight crew
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Surface speed/braking › Incorrect use/operation
Pilot
- Certificate: airline transport pilot, commercial pilot, flight engineer
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: no injuries
Co-pilot
- Certificate: airline transport pilot, flight instructor, commercial pilot
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Medical certificate: Class 1
- Seat: rgt
- Injury: no injuries
The aircraft
- Airframe total time: 1,321.9 hours
- Last inspection: continuous airworthiness programme, May 23, 2013
- Maximum gross weight: 35,450 lb
- Seats: 10
- Landing gear: retractable
- Engine 1: Pratt & Whitney Canada PW306A (turbofan); 1,322 hours total
- Engine 2: Pratt & Whitney Canada PW306A (turbofan); 1,322 hours total
- Operator: Taughannock Aviation
The flight
- Departed from: ROC Rochester NY
- Destination: JHW Jamestown NY
- Flight plan: IFR
- Runway 25, 5,299 ft by 100 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 72°F (22°C), dew point 48°F (9°C)
- Altimeter: 30.25 inHg
- Observation at 6:15 pm from JHW
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 3 | |||
| Passengers | 2 |
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.
