Cessna 150 and Cessna 525C accident near Marion, Indiana, April 2, 2018
On April 2, 2018 at about 7:09 pm local time, 2 aircraft, Cessna 150 (N5614E) and Cessna 525C (N511AC), were involved in the same accident near Marion, Indiana (Marion Municipal Airport). 2 people were killed; 5 others were unhurt. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 2, 2018 · about 7:09 pm local time
- Place
- Marion, Indiana · Marion Municipal Airport · map
- Type
- Accident · collision on the ground
- Injuries
- 2 people were killed; 5 others were unhurt.
- Weather
- visual conditions (good weather)
- Aircraft 1
- Cessna 150 UNDESIGNAT, built 1958 · all 150s on the register
- Registration
- N5614E · no longer on the register · serial 17114
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
- Aircraft 2
- Cessna 525C C, built 2012 · all 525Cs on the register
- Registration
- N511AC · registry record · serial 525C0081
- Damage
- Substantial damage
- Flight
- Business flight · general aviation rules (Part 91)
The NTSB's narrative for the Cessna 150 final · quoted from the NTSB record
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.
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 NTSB's narrative for the Cessna 525C final · quoted from the NTSB record
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.
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 for the Cessna 150 from the NTSB's investigation tables, in plain English
What happened, in order
- Ground collision during takeoff defining event
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Lack of action › Pilot
- cause Personnel issues › Action/decision › Action › Lack of action › Pilot of other aircraft
- factor Environmental issues › Physical environment › Runway/land/takeoff/taxi surface › (general) › Contributed to outcome
- factor Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › (general) › Contributed to outcome
- factor Personnel issues › Task performance › Communication (personnel) › Lack of communication › Pilot of other aircraft
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 71.9 hours in all; 10.6 in this make and model; 10.6 in the last 90 days; 8.6 in the last 30 days; 23.7 as pilot in command
- Last flight review: October 18, 2017
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 4,035 hours
- Last inspection: annual inspection, January 1, 2018
- Maximum gross weight: 1,499 lb
- Seats: 2
- Landing gear: fixed
- Engine: Cont Motor O-200 SERIES (piston); 4,035 hours total
- Fire on the ground
The flight
- Departed from: MZZ Marion IN at 7:08 pm
- Destination: MZZ Marion IN
- Flight plan: none
- Runway 15, 3,456 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 140° at 9 knots
- Visibility: 4 statute miles
- Sky: clear
- Temperature: 41°F (5°C), dew point 30°F (-1°C)
- Altimeter: 30.01 inHg
- Observation at 9:55 pm from MZZ
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
The factual record for the Cessna 525C from the NTSB's investigation tables, in plain English
What happened, in order
- Collision during takeoff/land during landing (landing roll) defining event
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Lack of action › Pilot
- cause Personnel issues › Action/decision › Action › Lack of action › Pilot of other aircraft
- factor Environmental issues › Physical environment › Runway/land/takeoff/taxi surface › (general) › Contributed to outcome
- factor Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › (general) › Contributed to outcome
- factor Personnel issues › Task performance › Communication (personnel) › Lack of communication › Pilot
Pilot
- Certificate: airline transport pilot
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instrument: airplane
- Flight time: 35,437 hours in all; 2,537 in this make and model; 67 in the last 90 days; 12 in the last 30 days; 35,237 as pilot in command
- Last flight review: June 24, 2017
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 2,537 hours
- Last inspection: annual inspection, March 9, 2018; 13 hours since
- Maximum gross weight: 17,100 lb
- Seats: 10
- Landing gear: retractable
- Engine 1: Williams FJ44-4A (turbojet); 2,537 hours total
- Engine 2: Williams FJ44-4A (turbojet); 2,537 hours total
The flight
- Departed from: JXN Jackson MI at 9:30 pm
- Destination: MZZ Marion IN
- Flight plan: IFR
- Runway 22, 6,011 ft by 100 ft
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 4 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check 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.