Practice Area

Aviation Litigation

Aircraft accidents, system failures, regulatory compliance — we build the technical exhibits that make complex aviation cases comprehensible to any jury.

Our Experience

Where Technical Precision Meets Courtroom Persuasion

Aviation litigation is among the most technically demanding work in civil practice. Juries are asked to evaluate avionics systems, navigation databases, cockpit procedures, regulatory standards, and engineering decisions — often in a matter of weeks. Legal-eze has the depth to support aviation cases at every level of complexity.

We create flight path reconstructions, cockpit systems diagrams, navigation database exhibits, regulatory compliance timelines, and cause-and-effect graphics that walk a jury through exactly what happened — technically and chronologically — and why the defendant bears responsibility. Every exhibit we build is developed in close collaboration with your aviation experts, engineers, and technical consultants.

We have worked on some of the most significant aviation litigation in history, including the American Airlines Flight 965 litigation against Honeywell and Jeppesen — a landmark case involving a fatal FMS navigation database defect that caused the deaths of 159 people in the mountains of Colombia.

What We Bring to Aviation Litigation

Flight path reconstructions — precise geographic exhibits mapping the aircraft's actual route against intended routing and terrain
Avionics and FMS system diagrams — illustrating how flight management systems work, where they failed, and why it mattered
Navigation database exhibits — showing data structure, identifier conflicts, and the chain of error from database to cockpit to catastrophe
Cockpit procedure timelines — reconstructing crew actions, ATC communications, and decision points in real time leading to the accident
Regulatory and certification exhibits — FAA and ICAO standard timelines showing what was required, what was certified, and where compliance failed
Hot-seat trial tech — managing complex technical databases, CVR/FDR data, radar tracks, and deposition clips throughout multi-week aviation trials
Case Study

American Airlines Flight 965

American Airlines v. Honeywell International & Jeppesen Sanderson — a landmark aviation products liability case involving a fatal flaw in the Flight Management System navigation database.

Accident Summary
Date
December 20, 1995
Aircraft
Boeing 757-223 · N651AA
Route
Miami → Cali, Colombia
Fatalities
159
of 163 aboard · 4 survivors
Cause
FMS navigation database defect — duplicate ICAO beacon identifier "R" caused FMC to navigate to Romeo (Bogotá) instead of Rozo (Cali)
Defendants
Honeywell International
FMC Manufacturer
Jeppesen Sanderson
Navigation Database Publisher
Legal-eze Role
All litigation graphics and trial presentation for American Airlines
The ICAO Standard

"Beacon identifiers shall not be duplicated within the same ICAO region unless the beacons are separated by more than 600 nautical miles."

Rozo (Cali) and Romeo (Bogotá) shared the identifier "R" — and were only 150 nautical miles apart. The database violated a standard in place since 1978.

The Accident — December 20, 1995

American Airlines Flight 965, a Boeing 757-200 operating from Miami International Airport to Alfonso Bonilla Aragón International Airport in Cali, Colombia, crashed into El Diluvio mountain in the Andes at approximately 9:40 PM local time. Of the 163 people on board, 159 perished — making it the deadliest aviation accident in Colombian history and, at the time, the most catastrophic accident involving a Boeing 757.

The flight crew — Captain Nicholas Tafuri, with over 13,000 hours of experience, and First Officer Donald Williams, with nearly 6,000 — were both highly skilled aviators. What killed them, and the 157 others aboard, was not pilot error alone. It was a defect in the navigation database that powered the aircraft's Flight Management System.

The Technical Defect — The "R" Identifier Problem

As Flight 965 descended toward Cali, the crew accepted a direct approach to runway 19, which required navigating to the Rozo NDB — a radio beacon near the airport identified as "R" on their Jeppesen approach chart.

When the captain entered "R" into the Flight Management Computer to navigate to Rozo, the FMC did not return Rozo. Instead, it returned Romeo — a completely different NDB located near Bogotá, 150 nautical miles to the northeast.

The root cause was a critical defect in the Honeywell FMC and the Jeppesen navigation database:

  • Duplicate identifiers within the same ICAO region. Both the Rozo NDB near Cali and the Romeo NDB near Bogotá used the single-letter identifier "R." ICAO standards in effect since 1978 prohibited duplicate identifiers unless the beacons were more than 600 nautical miles apart. These two were only 150 nautical miles apart — a clear violation. The database should never have allowed the conflict to exist.
  • The FMC displayed the wrong beacon first. When the captain typed "R" and selected from the list, the FMC presented Romeo — not Rozo — as the top result. The system provided no warning that two beacons shared the same identifier or that the selected waypoint was 150 miles in the wrong direction.
  • No alerting, no cross-check, no protection. Neither Honeywell's FMC nor Jeppesen's database provided any alert to the crew that a duplicate identifier conflict existed. The system silently redirected the autopilot toward Bogotá. By the time the error was detected, the 757 was in the wrong valley, on a collision course with a 9,800-foot mountain.

The aircraft struck El Diluvio mountain at approximately 9,700 feet. There were four survivors.

The Litigation — American Airlines v. Honeywell & Jeppesen

American Airlines brought suit against Honeywell International, manufacturer of the Flight Management Computer, and Jeppesen Sanderson, the publisher of the navigation database loaded into the FMC. The central claim: the navigation database was defective, the FMC failed to protect the crew from an identifier conflict that should never have existed, and the defendants' products — not the crew — were the proximate cause of the disaster.

Legal-eze handled all litigation graphics and trial presentation for the American Airlines case. Our team built the exhibits that explained, visually and precisely, how a single database defect — a duplicate beacon identifier in violation of longstanding ICAO standards — caused a modern commercial jet to turn toward the wrong mountain and kill 159 people.

What Legal-eze Built

The litigation required exhibits that could take an aviation system most jurors had never heard of — the Flight Management Computer — and make its failure so clear that there was no room for doubt. Our team produced:

  • Flight path reconstruction maps. Geographic exhibits showing the aircraft's intended routing into Cali versus the actual turn toward Bogotá — including terrain overlays, mountain elevations, and the point of impact.
  • FMC navigation database exhibits. Step-by-step visual breakdowns of how the "R" identifier conflict existed in the database, how the system presented Romeo instead of Rozo, and how ICAO standards expressly prohibited the duplication that caused the error.
  • Cockpit sequence timeline. A precise, second-by-second reconstruction of the crew's actions in the final minutes of flight — correlated with CVR transcript, FDR data, and ATC communications — showing the moment the wrong waypoint was selected and the chain of events that followed.
  • System design comparison exhibits. Demonstrating that a properly designed database and FMC would have flagged the duplicate identifier, presented the correct beacon, or warned the crew of the conflict — and that Honeywell and Jeppesen had the capability and the obligation to build that protection in.
Track Record

Aviation Results

Legal-eze has supported both Plaintiff and Defendant trial teams in aviation matters resulting in beneficial outcomes for our clients. Click below to view a small sampling of our case successes.

View Full Results →



Working an Aviation Case?

Tell us about it — we'll respond within 2 business hours.

Start a Conversation