Federal Express McDonnell Douglas DC-10 incident
McDonnell Douglas DC-10 and American International Airways Lockheed L-1O11-385-1-15 L-1O11-385 · Incident: near collision between aircraft en route
Event
- NTSB case
- CHI99IA100
- 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
- Incident
- 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
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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 · McDonnell Douglas DC-10
- Aircraft type
- McDonnell Douglas DC-10
- 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
- N40061
- Operator
- Federal Express
- Onboard fatalities
- Unknown
- Route
- From Portland International Airport (PDX), Portland, ORTo Frederick W. Smith International Airport (MEM), Memphis, TN
- 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
- 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
- First occurrenceThe 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
- Near collision between aircraft
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Aircraft 2 · Lockheed L-1O11-385-1-15 L-1O11-385
- Aircraft type
- Lockheed L-1
- 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
- N106CK
- Operator
- American International Airways
- Onboard fatalities
- Unknown
- Route
- From Los Angeles International Airport (LAX), Los Angeles, CATo Indianapolis International Airport (IND), 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 121: Air Carrier
- 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
- First occurrenceThe 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
- Near collision between aircraft
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Atc personnel(artcc) › IFR separation standards, not maintained
- Atc personnel(artcc) › Radio communications, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A Federal Express DC-10-10F sustained no damage during a near mid-air collision with an American International Airways Lockheed L-1011-385-1-15, 30 miles west of Salina, Kansas. The aircraft came within an estimated 1/2 mile horizontal and 0 feet vertical separation of each other. The FAA issued a Final Operational Error/Deviation Report. The report indicated that an ATC controller '...dropped the data block on FDX3207 [DC-10] without transferring communications...' to another controller. The report also indicated that another ATC controller, '...issued CKS303 [L-1011] a frequency change to 125.67 instead of the correct frequency of 127.65. CKS303 acknowledged the wrong frequency correctly by reading back 125.67.' ATC recognized that both airplanes were NORDO but were unable to reestablish radio communications, although several means were tried. The CKS303 First Officer reported he saw the DC-10 at their 8 o'clock position at 1/2 mile and same altitude. He reported he turned to the right 30 degrees. The FDX3207 pilots reported they did not see the L-1011 but felt its wake turbulence. Current FAA regulations do not require any aircraft used exclusively for cargo operations to be equipped with any version of TCAS.
Probable cause
the ARTCC personnel failed to maintain radio communications with both airplanes and failed to maintain IFR separation standards. Factors relating to the incident were the FAA does not require cargo airplanes to be equipped with TCAS and neither airplane was equipped with TCAS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI99IA100
- Event ID
- 20001205X00276
- Case number
- CHI99IA100
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, damage. 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.
- API snapshot SHA-256: 0eec8296d9052c83aefcfd110d2838794ceaf50146e415ebadb6c9bd61a868f9; retrieved 2026-09-18T16:58:54.227Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: operator. The NTSB narrative names the operator: "A Federal Express DC-10-10F sustained no damage during a near mid-air collision with an American International Airways Lockheed L-1011-385-1-15" The NTSB narrative names the operator: "A Federal Express DC-10-10F sustained no damage during a near mid-air collision with an American International Airways Lockheed L-1011-385-1-15"