# Incident 20000204002609I: Boeing 737222, Kansas City, MO, February 4, 2000

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: February 4, 2000, 07:35 local time
- Place: Kansas City, MO
- Airport: Kansas City International
- Phase of flight: To Init Climb(1st Pwr Reduct)
- Operating rules: Air carrier (Part 121)
- Operator: P2EA
- 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: N209US, a cancelled registration (https://openairdocs.org/deregistered/N209US-2018-01-16) (OpenAirDocs)
- Registry model: Boeing 737-222 (registry code 1384473, https://openairdocs.org/model/boeing-737-222) (OpenAirDocs)
- Registry engine: Pratt & Whitney JT8D-9 series (registry code 52048, https://openairdocs.org/engine/pratt-whitney-jt8d-9-series) (OpenAirDocs)
- Reported make and model: BOEING 737222
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000204002609I

## Narrative

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

(-5) ON FEBRUARY 4, 2000, VANGUARD AIRLINES, FLIGHT 297, A BOEING 737, WAS ENROUTE FROM MCI TO DEN. AFTER TAKE OFF THE PILOT REPORTED THAT HE HAD A GEAR PROBLEM AND REQUESTED TO RETURN TO MCI. NO EMERGENCY OR EQUIPMENT REQUESTED AND THE PILOT LANDED AT MCI WITH NO FURTHER INCIDENT. THE PILOT'S LOG PAGE WRITE UP READ THAT THE GEAR LEVER WOULD NOT MOVE UP AFTER TAKE OFF. THE TAKE OFF WARNING DID NOT REMAIN SILENT WITH FLAPS UP. VANGUARD MAINTENANCE REVEALED THAT THE RIGHT HAND MAIN LANDING GEAR TELEFLEX CABLE WAS OUT OF ADJUSTMENT. VANGUARD MAINTENANCE PERFORMED ADJUSTMENTS TO THE TELEFLEX CABLE AND PERFORMED A GEAR SWING. THE MAIN LANDING GEAR OPERATIONALLY CHECKED NORMAL AS PER, MM27-62-51A. THE AIRCRAFT WAS RETURNED TO SERVICE.

## Other reports on N209US (5)

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

- [Incident 20000102000949I](https://openairdocs.org/incident/20000102000949I), Jan 2, 2000: Boeing 737222 (N209US), Buffalo, NY. (-23) On Sunday, January 2, 2000, at 1239 local, a vanguard airlines B-737, N209US, flight 734 performed an air turnback due to the number one overheat light…
- [Incident 19981122040729I](https://openairdocs.org/incident/19981122040729I), Nov 22, 1998: Boeing 737222 (N209US), Kansas City, MO. (-5)Air carrier P2EA, flight number 408, B737-222, mci-atl, while enroute to atl the number two engine start valve illuminated shortly after takeoff from mci.…
- [Incident 19980112020379I](https://openairdocs.org/incident/19980112020379I), Jan 12, 1998: Boeing 737222 (N209US), Goshen, IN. Fuel unbalance problems due to right fuel tank transfer line became disconnected.
- [Incident 19911217062029I](https://openairdocs.org/incident/19911217062029I), Dec 17, 1991: Boeing 737222 (N209US), Baltimore, MD. Right nose wheel broke off while taxiing to runway. Found crack in axle at inner bearing race.
- [Incident 19900416016169I](https://openairdocs.org/incident/19900416016169I), Apr 16, 1990: Boeing 737222 (N209US), Charlotte, NC. Crew unable to pressurize airplane on climb. Returned. Found e and e compartment door opened.

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.