FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight 482 · Boeing 757-232

2 Jun 2002 · Fairfield, IL, United States

Boeing 757-232 · Accident en route

From DEN · Fairfield, IL to Cincinnati Northern Kentucky International Airport (CVG)

Report a problem

Event

NTSB case
NYC02LA110
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Boeing 757-232

Aircraft type
Boeing 757
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N694DL
Operator
Unknown
Onboard fatalities
Unknown
Route
From DEN · Fairfield, ILTo Cincinnati Northern Kentucky International Airport (CVG), Covington, KY
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 121: Air Carrier
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · descent
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Miscellaneous/other
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Copilot/second pilot › Level off, abrupt

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The captain reported that during a descent in IMC conditions, the traffic collision avoidance system (TCAS) sounded "traffic, traffic, traffic." The TCAS displayed a target 700 feet below, and 15 miles ahead of the flight. However, the TCAS did not issue a resolution advisory. The flight crew could not visually identify the traffic, and the captain instructed the first officer to stop the descent. The first officer disconnected the autopilot and then "quickly" leveled the airplane. During the level off, a flight attendant fell and suffered a fractured leg. Subsequently, a review of the TCAS and check with ATC revealed that the traffic was at FL 260, not FL 270. A review of the airline's operations manual revealed that deviation from an ATC clearance was authorized for a resolution advisory.

Probable cause

The first officer's abrupt level off.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC02LA110
Event ID
20020625X00969
Case number
NYC02LA110
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, damage. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 421117bbc35114d6524ccbefe6dc4a0faf2337ee959ae23d3ba14d3e445e2bae; retrieved 2026-09-18T16:02:19.215Z.