853
1969-SEP-09 · Fairland, Indiana

Multi-aircraft Event — Allegheny Airlines AL853 / Forth Corporation (Leased) N7374J

Allegheny Airlines Flight 853, a DC-9-31, collided mid-air with a Piper PA-28-140 light aircraft while descending toward Indianapolis. The collision occurred at approximately 3,550 feet when the Piper's left wing struck the DC-9's tail assembly, shearing off the horizontal stabilizer. Both aircraft crashed with no survivors. The investigation highlighted the failure of the 'see and avoid' concept in mixed IFR/VFR traffic environments and the limitations of the air traffic control system at the time.

Aircraft 1
Allegheny Airlines — Flight AL853
McDonnell Douglas DC-9-31 · N988VJ
Cincinnati/Northern Kentucky Airport, KYIndianapolis-Weir Cook Municipal Airport, IN
Souls 82 · Fatal 82
Aircraft 2
Forth Corporation (Leased) — Flight N7374J
Piper PA-28-140 · N7374J
Brookside Airpark, INBakalar AFB, IN
Souls 1 · Fatal 1
Phase
En route
Cause
Human Factors (Operational)
Total Souls
83
Total Fatalities
83
Report
Final Report

Investigation Summary

The DC-9 was operating under Instrument Flight Rules (IFR) and was under positive radar control, descending from 6,000 feet to an assigned 2,500 feet. The Piper PA-28 was being flown by a student pilot on a solo cross-country flight under Visual Flight Rules (VFR) at 3,500 feet. Although visibility was 15 miles, intervening clouds and the relative positions of the aircraft prevented the crews from seeing each other until seconds before impact. The Indianapolis approach controller did not observe the Piper's primary radar target, which lacked a transponder, and thus did not issue a traffic advisory to the DC-9 crew.

Final Conclusions

The NTSB determined the probable cause was the deficiency in the collision avoidance capability of the ATC system in a terminal area with mixed IFR and VFR traffic. Contributing factors included the inadequacy of the see-and-avoid concept, technical limitations of radar in detecting small aircraft without transponders, and the lack of regulations providing adequate separation for mixed traffic in terminal areas.

Video Analysis

An Almost Forgotten Crash That Made Flying Safer | Allegheny Airlines Flight 853 — The story of Allegheny Airlines Flight 853 and the mid-air collision over Indiana that led to significant changes in air traffic control and terminal area regulations.

If playback is blocked, the owner has disabled embedding — use the link above.

Airframe & Maintenance

Allegheny Airlines AL853 — McDonnell Douglas DC-9-31 · N988VJ

Airframe Hours
3,170
Cycles
3,752
Engines
Pratt & Whitney JT8D-7

Crew Experience

Allegheny Airlines AL853 — McDonnell Douglas DC-9-31 · N988VJ

Captain

Total hours
23,800

Captain James M. Elrod

First Officer

Total hours
2,850

First Officer William T. Heckendorn

Forth Corporation (Leased) N7374J — Piper PA-28-140 · N7374J

Student Pilot

Total hours
46

Robert N. Carey

Systems & Failure Modes

i

See-and-Avoid

The primary method of collision avoidance for VFR flight, which proved inadequate due to closure speeds and cloud interference.

i

Primary Radar

The ATC radar relied on physical reflections for the Piper, which were insufficient for the controller to identify the conflict.

i

Horizontal Stabilizer

The DC-9's T-tail stabilizer was destroyed in the collision, rendering the aircraft unflyable.

Interesting Facts

  • 01The DC-9's tail assembly was sheared off by the Piper's left wing, leading to an immediate loss of control.
  • 02The DC-9 impacted the ground in an inverted, nose-down attitude.
  • 03The Piper PA-28 was not equipped with a transponder, making it difficult to detect on the radar systems of the era.
  • 04The collision occurred just two seconds after the DC-9 first officer likely made a required 3,500-foot altitude call.
  • 05The student pilot of the Piper was wearing glasses and had his anti-collision beacon on at departure.

Safety Actions & Advisories

Radar Reflectivity Standards

The NTSB recommended establishing minimum standards for the radar reflectivity of small aircraft to improve detection.

Scanning Training

Mandatory aircrew training programs were recommended to improve effective visual scanning patterns and procedures.

Terminal Area Separation

The accident accelerated the development of Terminal Control Areas (now Class B airspace) to strictly segregate VFR and IFR traffic.

Location

Fairland, Indiana · 39.6172, -85.9206

Related Cases

Case ID · allegheny-853-1969Last updated · Filed

© 2026 TechBridge Software Co., Ltd. — BlackBoxWiki is an open aviation reference. Not affiliated with any aviation authority.