# Incident 20230213002289I: Dassault Aviation FALCON 2000EX, Dayton, OH, February 13, 2023

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: February 13, 2023, 12:44 local time
- Place: Dayton, OH
- Damage: No damage
- Phase of flight: Climb
- Operating rules: General operating rules (Part 91)
- Location: 39.7589° N, 84.1916° W: Placed by OpenAirDocs: center of Dayton, OH, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.7589&lon=-84.1916&mi=10
- Aircraft: N501N, registered now (https://openairdocs.org/aircraft/N501N) (OpenAirDocs)
- Registry model: Dassault FALCON 2000EX (registry code 2730110, https://openairdocs.org/model/dassault-falcon-2000ex) (OpenAirDocs)
- Registry engine: Pratt & Whitney Canada PW308C (registry code 52182, https://openairdocs.org/engine/pratt-whitney-canada-pw308c) (OpenAirDocs)
- Reported make and model: DASSAULT AVIATION FALCON 2000EX
- Reported engine: P&W CANADA PW308C
- People aboard: 4
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Airline transport
- Pilot flight hours: 20,174 total, 706 in this make and model, 74 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20230213002289I

## Narrative

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

ON FEBRUARY 13, 2023, ^PRIVACY DATA OMITTED^ WAS TO CLIMBING TO THE CLEARED ALTITUDE OF FLIGHT LEVEL 350.  AIR TRAFFIC CONTROL ADVISED ^PRIVACY DATA OMITTED^ THERE WAS TRAFFIC AT THEIR 10 O’CLOCK POSITION DESCENDING TO FLIGHT LEVEL 360.  AS ^PRIVACY DATA OMITTED^ WAS CLIMBING THROUGH FLIGHT LEVEL 330 - FLIGHT LEVEL 340 WITH THE AUTOPILOT ENGAGED A “TRAFFIC” ALERT WAS ISSUED BY THE AIRCRAFT’S TCAS SYSTEM.  A FEW SECONDS AFTER THE “TRAFFIC” ALERT, A RESOLUTION ALERT (RA) TO “LEVEL OFF” WAS ISSUED AS THE AIRCRAFT’S AUTOPILOT STARTING TO LEVEL THE AIRCRAFT AT FLIGHT LEVEL 350.  THE PILOT DISENGAGED THE AUTOPILOT TO RESPOND TO THE RA TO FOLLOW THE COMMAND GUIDANCE BARS.  ^PRIVACY DATA OMITTED^ AND THE OTHER AIRCRAFT REPORTED TO ATC THEY WERE RESPONDING TO A RESOLUTION ALERT.  A FEW SECONDS AFTER ^PRIVACY DATA OMITTED^ REPORTED THE RA, THEY RECEIVED ANOTHER RA TO “CLIMB, CLIMB”.  THE PILOT FOLLOWED THE TCAS GUIDANCE BARS TO CLIMB.  ANOTHER RA TO “INCREASE CLIMB, INCREASE CLIMB” FOLLOW IMMEDIATELY AFTER THE “CLIMB, CLIMB” RA.  THE PILOT RESPONDED TO THE RA BY CONTINUING THE CLIMB BY FOLLOWING THE TCAS GUIDANCE BARS.  A FEW SECONDS LATER A RA OF “CLEAR OF CONFLICT” WAS RECEIVED.  THE AIRCRAFT FLEW ABOUT 300 FEET ABOVE THE ASSIGNED FLIGHT LEVEL 350 DURING RA.  ^PRIVACY DATA OMITTED^ NOTIFIED ATC THEY WERE FINISHED RESPONDING THE RA AND WAS RETURNING TO FLIGHT LEVEL 350. THERE WAS NO FURTHER COMMUNICATION FROM ATC REGARDING ^PRIVACY DATA OMITTED^ REPORTED RA.

WHEN THE PILOT RECEIVED THE RA ALERTS, HE FOLLOWED THE TCAS RESOLUTION ADVISORY PROCEDURE IN THE FALCON 2000EX EASY’S QRH VOLUME II.  NO FURTHER ACTIONS TAKEN AT THIS TIME.

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.