# Incident 20000122001149I: Amd FALCON20, Kansas City, MO, January 22, 2000

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 22, 2000, 05:00 local time
- Place: Kansas City, MO
- Airport: Kansas City International
- Phase of flight: Final Approach
- Operating rules: Air carrier (Part 121)
- Operator: Y2PA
- Location: 39.2976° N, 94.7139° W: Placed by OpenAirDocs at KANSAS CITY INTL (MCI), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.2976&lon=-94.7139&mi=10
- Aircraft: N818AA, a cancelled registration (https://openairdocs.org/deregistered/N818AA-2015-05-06) (OpenAirDocs)
- Registry model: Dassault-Breguet FALCON 20 (registry code 2730103, https://openairdocs.org/model/dassault-breguet-falcon-20) (OpenAirDocs)
- Registry engine: GE CF700 series (registry code 30010, https://openairdocs.org/engine/ge-cf700-series) (OpenAirDocs)
- Reported make and model: AMD FALCON20
- People aboard: 2
- Fatal injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000122001149I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) ON JANUARY 22, 2000, USA JET AIRLINES FALCON-20, N818AA, WAS INBOUND TO KANSAS CITY INTERNATIONAL AIRPORT (MCI), AND DECLARED AN EMERGENCY DUE TO UNSAFE GEAR INDICATION.  AIRCRAFT LANDED WITHOUT INCIDENT.  CONTRACT AIRCRAFT MAINTENANCE (CAM) INSPECTED AIRCRAFT FOR FERRY PERMIT TO DETROIT, MI (YIP) FOR REPAIRS BY USA JET PERSONNEL.  A BROKEN WIRE WAS FOUND IN GEAR HANDLE.  INCIDENT #CE2000IAC018 IS CONSIDERED CLOSED WITH THIS REPORT.

## Other reports on N818AA (1)

Matched to the same aircraft by N-number and date.

- [Incident 19940405014709I](https://openairdocs.org/incident/19940405014709I), Apr 5, 1994: Avianw FALCON2 (N818AA), Sparta, TN, Minor damage. Brakes did not slow aircraft down on rollout. Deaparted end of runway. Tires showed signs of hydroplaning.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.