# Incident 19960130002879I: Amd FALCON2000, Salina, KS, January 30, 1996

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 30, 1996, 11:55 local time
- Place: Salina, KS
- Damage: Minor damage
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 38.8107° N, 97.6146° W: Placed by OpenAirDocs: center of Salina, KS, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=38.8107&lon=-97.6146&mi=10
- Aircraft: N790L (not matched to a registry record)
- Reported make and model: AMD FALCON2000
- People aboard: 5
- Fatal injuries: 0
- Pilot flight hours: 10,000 total, 50 in this make and model, 60 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19960130002879I

## Narrative

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

NARRATIVE: ON JANUARY 30, 1996, AT 1755Z (11:55 CST), A DASSAULT FALCON JET 2000, OWNED BY DASSAULT FALCON JET CORPORATION AND OPERATED BY IBM CORPORATION, WHILE EN ROUTE TO LONG BEACH, CALIFORNIA, INCURRED DAMAGE TO THE PILOT'S LEFT WINDSHIELD OUTER PANE. SKIES WERE CLEAR AND THE AIRCRAFT WAS ON AN IFR FLIGHT PLAN. DAMAGE WAS CONFINED TO THE PILOT'S OUTER WINDSHIELD PANE AND STAYED INTACT. THE OUTER WINDSHIELD PANE HAD SHATTERED UNEXPECTEDLY. AN EMERGENCY DESCENT WAS MADE AT FLIGHT LEVER 45,000 FEET, 70NM WEST OF SALINA, KANSAS, WITH AN UNEVENTFUL LANDING AT THE WICHITA, KANSAS MID-CONTINENT AIRPORT. NO INJURIES OR OTHER AIRCRAFT DAMAGE WERE NOTED. THE PILOT'S LEFT WINDSHIED WAS REMOVED AND REPLACED BY RAYTHEON AIRCRAFT SERVICES WITH A DASSAULT TECHNICAL REPRESENTATIVE ASSIST AND APPROVED FOR RETURN TO SERVICE. PILOT BRIAN HUGHES CURRENTLY HOLDS AN ATP, NO 2184806. THE FLIGHT ORIGINATED FROM WHITE PLAINS, NEW YORK. THE AIRCRAFT WAS UNDER PART 91 THE DAY THE INCIDENT OCCURRED. THIS REPORT CLOSES THE INCIDENT.

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.