Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

November 30, 2003 · Cessna C172R · N9968F

Lexington, KY

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
November 30, 2003
Injury Outcomes
No injuries (2 uninjured)
Location
Lexington, KY
Aircraft
Cessna C172R
Tail Number
N9968F
Injuries
None
Aircraft Damage
Substantial
NTSB Number
IAD04LA003

The ground controller cleared regional jet mechanics to perform a static engine run at the gate, and advised that she would "take the Cessna up to a different intersection." She also cautioned another crew about the run-up; however, she did not mention the runup in her position relief briefing. The pilot of the accident airplane subsequently requested clearance to taxi, and the new ground controller granted the clearance without providing information about the regional jet's engine run-up. When the accident airplane passed about 300 feet behind the regional jet, it was blown sideways, struck its left wing on the ground, tipped onto its nose, and pivoted 180 degrees. The airplane continued to be buffeted until the mechanics were advised to cease the engine run-up. Federal Aviation Administration Order 7110.65P included a standard operating procedure about transferring position responsibility, which stated, "the specialist being relieved shall be responsible for ensuring that any pertinent status information of which he/she is aware is relayed to the relieving specialist..."

NTSB Probable Cause

The ground controller's failure to advise the relieving controller information regarding an engine run-up, which subsequently resulted in the flight instructor's inadvertent encounter with jet blast during ground taxi.

Full Narrative

On November 30, 2003, at 1241 eastern standard time (EST), a Cessna 172R, N9968F, was substantially damaged while taxiing at Blue Grass Airport (LEX), Lexington, Kentucky. The certificated flight instructor and the non-certificated student pilot were not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the local instructional flight conducted under 14 CFR Part 91. According to a statement submitted by the flight instructor, while taxiing for takeoff, as the airplane passed behind a Canadair CL-600 CRJ, it began to slide sideways, and the left wing struck the ground. The airplane then tipped onto its nose, and pivoted about 180 degrees. As it did so, the instructor shut down the engine. The airplane then came back down on the main landing gear, but continued to "buffet," and began to "fly backwards" in the CRJ's jet blast. A safety representative from the CRJ operator reported that there were two mechanics onboard the airplane to evaluate a cabin smoke discrepancy. While troubleshooting the problem, it was necessary to perform a static engine run at high power for 20-30 minutes. The airplane was chocked, near gate C-5, with the tail pointing north. In addition, there were two employees from an affiliated company in front of the airplane, supervising the operation. A review of air traffic control (ATC) voice recordings revealed that at 1151, one of the mechanics in the CRJ contacted the ground controller, and inquired as to where he could perform a high power engine run-up. The ground controller stated that the mechanic could perform his run-up at the gate and that she would "take the Cessna up to a different intersection." The mechanic then stated that once another airplane in front of his pushed back, he'd advise her that he'd be starting and running the engines. At 1152, the controller stated that if the mechanic didn't want to do the run-up at the gate, he could do it on the other side of the runway. The mechanic replied that he would see how long it took for the other airplane to push back and how long it would take for his company's operations personnel to arrive, and that he'd advise the ground controller at that point as to what he'd be doing. At 1201, the mechanic advised the ground controller that he would perform the run-up at the gate once the airplane in front of him was pushed back. At 1221, a pilot in the airplane in front of the CRJ requested, and was cleared to taxi to the runway. The ground controller also stated, "use caution for that r-j off your right wing doing an engine run up." At 1230, the ground controller began briefing a relieving ground controller. There was no mention of the CRJ engine run-up during the briefing. At 1236, the flight instructor in the Cessna contacted the new ground controller, who cleared him to taxi to the runway. At 1241, the flight instructor advised the new ground controller that he'd need a tow, and shortly thereafter asked, "could you have [the CRJ] redirect his jet blast please?" The controller replied, "we're working on it." One of the employees who was supervising the engine run-up from the outside of the airplane then got the mechanics' attention. The engine run-up was discontinued, and the engines were shut down. According to the safety representative from the CRJ operator, airport police estimated that the Cessna was about 300 feet behind the CRJ when the accident occurred. Federal Aviation Administration (FAA) Order 7110.65P, Air Traffic Control, Appendix D, Standard Operating Practice for the Transfer of Position Responsibility, stated: "the specialist being relieved shall be responsible for ensuring that any pertinent status information of which he/she is aware is relayed to the relieving specialist...." The weather reported at Lexington, at 1254, included winds from 230 degrees true at 16 knots, 10 miles visibility, no clouds below 12,000 feet, temperature 52 degrees Fahrenheit, dew point 32 degrees Fahrenheit, and a barometric pressure of 30.07 inches of mercury.

Flight

Event TypeAccident
Event Time12:41 EST
Nearest AirportLexington Bluegrass Airport (0nm)
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna C172R
Tail NumberN9968F
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-360-LA · Reciprocating · 160
Seats4

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 21 · First Class · None
Crew 2Age 31 · None · None

Conditions

ConditionsVMC
LightDaylight
Wind230° @ 16 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point52 / 32 C
Altimeter30.06 inHg
Observation Time17:54
Weather SourceWFAC

Appendix: Source Data