Allegheny Airlines Flight 853
Piper PA-28 and Douglas DC-9 · Mid-air collision
Event
- 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
- Unknown
- Event fatalities
- 83 · all aircraft and ground
- Ground fatalities
- 0
- Occupants
- 83
- Survivors
- 0
- 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
- Airline
- 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 · Piper PA-28
- Aircraft type
- Piper PA-28
- 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
- N7374J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Occupants
- 1
- Survivors
- 0
- 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
- None · no survivors
- Route
- From Indianapolis, INTo Indianapolis, IN
- 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 91: General aviation (fixed base operator)
- 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 · cruise
- 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 with aircraft - both in flight
- 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 · Douglas DC-9
- Flight
- AL853
- Aircraft type
- Douglas DC-9
- 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
- N988VJ
- Operator
- Allegheny Airlines
- Onboard fatalities
- Unknown
- Occupants
- 82
- Survivors
- 0
- 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
- None · no survivors
- Route
- From Boston, MATo St Louis, MO
- 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 (scheduled domestic passenger service)
- 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
- 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 with aircraft - both in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Miscellaneous › Written cause
Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.
From the Wikipedia article
On September 9, 1969, Allegheny Airlines Flight 853, a McDonnell Douglas DC-9 operating a regularly scheduled flight from Boston, Massachusetts, to St. Louis, Missouri, with stops in Baltimore, Maryland; Cincinnati, Ohio; and Indianapolis, Indiana, collided mid-air with a Piper PA-28 light aircraft near Fairland, Indiana. The left wing of the PA-28 sheared off the DC-9's rear tail assembly, causing both to crash, killing all 83 occupants on board both aircraft. More than 50 years later, the incident remains Indiana's deadliest commercial airline disaster.
Flight history
Allegheny Airlines Flight 853 was a regularly scheduled flight departing Boston Logan International Airport with a final destination of St. Louis International Airport (Lambert Field) with stopovers at Baltimore Friendship (now known as Baltimore-Washington International Airport), Greater Cincinnati (now known as Cincinnati/Northern Kentucky International), and Indianapolis Weir-Cook Municipal Airport (now known as Indianapolis International). The aircraft, N988VJ, was a McDonnell Douglas DC-9-31 manufactured in 1968 with 3170 hours on the airframe at the time of the incident. At the controls were Captain James Elrod, 47, a seasoned veteran with more than 23,800 flight hours, and First Officer William Heckendorn, 26. The flight departed from Cincinnati at 3:15 pm en route to Indianapolis, carrying 78 passengers and 4 crew members. Flying under instrument flight rules (IFR), it was initially cleared to ascend to airway V-97 at 10,000 feet. Approach Control then instructed it to descend to 6,000 ft; then 2,500 ft after passing the Shelbyville VOR. The flight was then vectored to a 280 degree heading. This was the last recorded communication between Air Traffic Control and the aircraft.
The other aircraft, a privately owned Piper PA-28, was piloted by 34-year-old Robert Carey. He was attempting a solo cross-country flight, and was on a southeasterly heading. It departed Brookside Airpark at 3:21 pm, operating under a visual flight rule (VFR) flight plan which indicated a cruising altitude of 3,500 ft. It was not in communication with air traffic control and was not equipped with a transponder, and there was no evidence it appeared as a primary radar target on the radarscope. Though visibility was 15 miles, an intervening cloud condition prevented either aircraft from seeing the other until a few seconds prior to the collision.
With only a window of 14 seconds to see and react, neither aircraft nor the Air Traffic Controller noticed the impending collision, with the pilots of the DC-9 likely preparing for a 3,500 ft altitude call. The two aircraft converged at a relative speed of 350 mph, 4 miles northwest of Fairland, Indiana, at an altitude of 3,550 feet. The initial point of impact was at the forward upper right section of the DC-9's vertical stabilizer, just underneath the horizontal stabilizer. On the Piper, the impact point was just forward of the left wing root. The impact severed the entire tail assembly of the DC-9, which rolled left until it was inverted and crashed nose-down into a soybean field at an approximate speed of 400 mph, about 100 yd north of the Shady Acres mobile home park. The PA-28 broke up mid-air and crashed approximately 4500 ft from the DC-9.
Investigation and cause
Probable cause
The National Transportation Safety Board released the following probable cause in a report adopted July 15, 1970:
The Board determines the probable cause of this accident to be the deficiencies in the collision avoidance capability of the Air Traffic Control system of the FAA in a terminal area wherein there was mixed instrument flight rules (IFR) and visual flight rules (VFR) traffic. The deficiencies included the inadequacy of the see-and-avoid concept under the circumstances of this case; the technical limitations of radar in detecting all aircraft; and the absence of Federal Aviation Regulations which would provide a system of adequate separation of mixed VFR and IFR traffic in terminal areas.
Text from the Wikipedia article “Allegheny Airlines Flight 853” (revision 1339313305, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article
NTSB remarks
RADAR LIMITATIONS.SEE AND AVOID CONCEPT INADQT. MISC-DEFICIENCIES IN ATC COLLISION AVOIDANCE SYS.
INADQT SEPN OF MIXD IFR AND VFR TFC IN TRML AREAMISC-DEFICIENCIES IN ATC COLLISION AVOIDANCE SYS.
NTSB's remark from its 1962–1981 archive, as recorded (abbreviated, at most 98 characters): the archive has no narrative
Sources
Wikipedia article: Allegheny Airlines Flight 853
- Revision
- 1339313305 · 2026-02-19 · retrieved 2026-09-18
- Wikidata
- Q4731275
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record
- Event ID
- 19690909P028512
- Case number
- Unknown
- Dataset
- historical-pre1982
- Source SHA-256
- abe1a933b4b73583d61684309f7f0610c281e3c1de3537c6471bf2a98ba6481d
Where each value comes from
- Record
- Wikipedia article "Allegheny Airlines Flight 853" (page 4336311, revision 1339313305); merged with NTSB case NTSB19690909P028512 (PRE1982 tblFirstHalf (one row per aircraft, grouped by date, place and time))
- Date
- NTSB record NTSB19690909P028512: PRE1982 DATE_OCCURRENCE
- Place and country
- Wikipedia infobox: site; country from NTSB record NTSB19690909P028512
- Map position
- Wikipedia: Wikipedia article coordinates
- Aircraft, operator and route
- NTSB record NTSB19690909P028512: PRE1982 REGIST_NO, ACFT_MAKE, ACFT_MODEL; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
- Operation
- NTSB record NTSB19690909P028512: operated under Part 91: General aviation (fixed base operator), Part 121: Air carrier (scheduled domestic passg.svc)
- Fatalities
- NTSB record NTSB19690909P028512: PRE1982 TOTAL_ABRD_FATAL of each aircraft, plus people on the ground and others outside the aircraft
- Ground fatalities
- NTSB record NTSB19690909P028512: events.inj_f_grnd
- Summary
- Wikipedia infobox: summary
Source notes (4)
- One occurrence in two sources, merged: the Wikipedia article "Allegheny Airlines Flight 853" and NTSB case NTSB19690909P028512, 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.
- From NTSB's 1962-1981 archive (PRE1982), which holds at most a short remark (98 characters, abbreviated) instead of a narrative; the accident type, phase of flight, causes and conditions are NTSB's codes, decoded as the archive defines them.
- Reviewed means this record passed the site's consistency check, not that it was checked against a narrative or report - there is none to check against.
- The operation category is mapped from the archive's operator and operation codes and has not been reviewed.