Marion Municipal Airport collision
Cessna 150 UNDESIGNAT and Cessna 525C C · Runway incursion
Event
- NTSB case
- CEN18FA132
- 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
- Event fatalities
- 2 · all aircraft and ground
- Ground fatalities
- Unknown
- Occupants
- Unknown
- Survivors
- 5
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- 0 serious · 0 minor (NTSB)
- 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
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Aircraft 1 · Cessna 150 UNDESIGNAT
- Aircraft type
- Cessna 150
- 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
- N5614E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Marion Municipal Airport (MZZ), Marion, INTo Marion Municipal Airport (MZZ), Marion, IN
- Aircraft age
- About 60 years (built 1958)
- 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 91: General Aviation
- 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
- Takeoff
- Defining eventThe 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
- Ground collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Aircraft 2 · Cessna 525C C
- Aircraft type
- Cessna 525
- 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
- N511AC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Occupants
- Not stated
- Survivors
- 5
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- Not stated
- Route
- From Jackson County Airport/Reynolds Field (JXN), Jackson, MITo Marion Municipal Airport (MZZ), Marion, IN
- Aircraft age
- About 6 years (built 2012)
- 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 91: General Aviation
- 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
- Landing · landing roll
- Defining eventThe 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
- Collision during takeoff/landing
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
From the Wikipedia article
Unless otherwise noted, all times in this article are UTC-4.
The Marion Municipal Airport collision occurred on 2 April 2018 at Marion Municipal Airport in Marion, Indiana, United States, killing 2 people.
Similar accidents
Tenerife airport disaster: a collision on the runway at Tenerife North Airport on 27 March 1977, killing 583 people.
Linate Airport disaster: a runway collision at Milan Linate Airport on 8 October 2001, killing 118 people.
All Nippon Airways Flight 25 disaster (1960): a collision between a civil airliner and a military aircraft at Nagoya Airfield on 16 March 1960, killing 3 people.
Translated into English with AI assistance from the Chinese Wikipedia article “馬里恩市機場撞機事故” (revision 94264452, retrieved 2026-09-19) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out; the translation may contain errors, and long articles were cut to their first 700 words. Read the article
NTSB narrative
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
Chinese Wikipedia article: 馬里恩市機場撞機事故
- Article
- 馬里恩市機場撞機事故
- Translation
- Into English with AI assistance; names of linked operators and aircraft types from Wikidata. It may contain errors.
- Revision
- 94264452 · 2026-09-09 · retrieved 2026-09-19
- Wikidata
- Q55698239
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record CEN18FA132
- Event ID
- 20180403X00427
- Case number
- CEN18FA132
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
- Record
- zh Wikipedia article "馬里恩市機場撞機事故" (page 6103361, revision 94264452), translated into English with AI assistance; merged with NTSB case CEN18FA132 (events / aircraft)
- Date
- NTSB record CEN18FA132: NTSB API eventDate, eventTimeUtc and eventTimeUtcOffsetHours (local date)
- Place and country
- Wikipedia infobox: site; country from NTSB record CEN18FA132
- Map position
- NTSB record CEN18FA132: events decimal coordinates
- Aircraft, operator and route
- NTSB record CEN18FA132: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
- Operation
- NTSB record CEN18FA132: operated under Part 91: General Aviation
- Fatalities
- NTSB record CEN18FA132: NTSB API totalFatal
- Ground fatalities
- NTSB record CEN18FA132: events.inj_f_grnd
- Summary
- Wikipedia infobox: summary
Source notes (3)
- One occurrence in two sources, merged: the Wikipedia article "Marion Municipal Airport collision" and NTSB case CEN18FA132, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
- Filled from the NTSB case API where the bulk record had no value: investigation status. 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.