Takeoff & Initial Climb · NTSB CEN18FA132

CESSNA 525C — Marion, IN

2 fatal High-time pilot
DateApril 2, 2018
LocationMarion, IN
AircraftCESSNA 525C
Purpose of flightBusiness
ConditionsDay · Visual Meteorological Cond
Phase / occurrenceLanding-landing roll Collision during takeoff/land
Pilot age70
Pilot total time35,437 hrs · High time
Time in type2,537 hrs
Fatalities2

Probable cause

The failure of both pilots to see and avoid the other airplane as they converged on intersecting runways. Contributing to the accident was the jet pilot's not monitoring the airport's traffic advisory frequency, known reduced visibility of the intersecting runways, and hazy weather condition.

NTSB findings

  • Personnel issues-Action/decision-Action-Lack of action-Pilot - C
  • Personnel issues-Action/decision-Action-Lack of action-Pilot of other aircraft - C
  • Environmental issues-Physical environment-Runway/land/takeoff/taxi surface-(general)-Contributed to outcome - F
  • Environmental issues-Conditions/weather/phenomena-Ceiling/visibility/precip-(general)-Contributed to outcome - F
  • Personnel issues-Task performance-Communication (personnel)-Lack of communication-Pilot - F

What happened

A single-engine airplane was taking off from runway 15 about the same time that a multi-engine business jet landed on a nearly perpendicular runway (runway 22). The single-engine airplane, piloted by a private pilot, was departing on a local flight. The jet, piloted by an airline transport pilot, was rolling down the runway following a straight-in visual approach and landing. The single-engine airplane collided with the empennage of the jet at the intersection of the two runways. Witnesses in the airport lounge area heard the pilot of the single-engine airplane announce on the airport's universal communications (UNICOM) traffic advisory frequency a few minutes before the accident that the airplane was back-taxiing on the runway. The pilot of the jet did not recall making any radio transmissions on the UNICOM frequency and review of the jet's cockpit voice recorder did not reveal any incoming or outgoing calls on the frequency. The pilots of both airplanes were familiar with the airport, and the airport was not tower controlled.

The airport had signage posted on all runways indicating that traffic using the nearly perpendicular runway could not be seen and instructed pilots to monitor the UNICOM. A visibility assessment confirmed reduced visibility of traffic operating from the nearly perpendicular runways. The reported weather conditions about the time of the accident included clear skies with 4 miles visibility due to haze. Both airplanes were painted white.

It is likely that the pilot of the jet would have been aware of the departing traffic if he was monitoring the UNICOM frequency. Although the jet was equipped with a traffic collision avoidance system (TCAS), he reported that the system did not depict any conflicting traffic during the approach to the airport. Although the visibility assessment showed reduced visibility from the departing and arrival runways, it could not be determined if or at what point during their respective landing and takeoff the pilot of each airplane may have been able to see the other airplane. In addition to the known reduced visibility of the intersecting runways, both airplanes were painted white and there was reported haze in the area, which could have affected the pilots' ability to see each other.

An editorial "what led to it / how to avoid it" analysis for this accident is generated separately and will appear here.

View the official NTSB docket →