# Incident 20260904011909I: Airbus A320-232, New York, NY, September 4, 2026

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: September 4, 2026, 21:07 local time
- Place: New York, NY
- Airport: John F Kennedy International
- Damage: No damage
- Phase of flight: Takeoff: Climb Out
- Operating rules: Air carrier (Part 121)
- Operator: YENA
- Location: 40.6399° N, 73.7787° W: Placed by OpenAirDocs at JOHN F KENNEDY INTL (JFK), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=40.6399&lon=-73.7787&mi=10
- Aircraft: N592JB, registered now (https://openairdocs.org/aircraft/N592JB) (OpenAirDocs)
- Registry model: Airbus A320-232 (registry code 3940004, https://openairdocs.org/model/airbus-a320-232) (OpenAirDocs)
- Registry engine: IAE V2500SERIES (registry code 34601, https://openairdocs.org/engine/iae-v2500series) (OpenAirDocs)
- Reported make and model: AIRBUS A320-232
- Reported engine: IAE V2500SERIES
- People aboard: 137
- Fatal injuries: 0
- Other injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20260904011909I

## Narrative

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

THE FLIGHT CREW EXPERIENCED AN EXCEPTIONALLY LONG TAXI SEQUENCE INVOLVING MULTIPLE REROUTES, REQUIRING THEM TO SHUT DOWN AN ENGINE AND RESTART IT JUST MINUTES PRIOR TO DEPARTURE. ONCE CLEARED, THE FIRST OFFICER (FO), ACTING AS THE PILOT FLYING, EXECUTED A NORMAL TAKEOFF.

AS THE AIRCRAFT CLIMBED THROUGH APPROXIMATELY 7,000 FEET, THE CAPTAIN WAS IN THE PROCESS OF CHECKING IN ON A NEW RADIO FREQUENCY WHEN THE CREW HEARD A DISTINCT IMPACT AGAINST THE AIRFRAME. THE CAPTAIN IMMEDIATELY ASKED THE FO IF HE HAD SEEN ANYTHING OUT THE WINDOW. THE FO REPORTED THAT HE BELIEVED THEY HAD STRUCK A DRONE. HE EXPLAINED THAT IN THE SPLIT SECOND BEFORE THE COLLISION, HE HAD CAUGHT A GLIMPSE OF WHAT APPEARED TO BE ARTIFICIAL LIGHTS. BECAUSE DRONES ARE INCREASINGLY COMMON AIRSPACE HAZARDS AND ARE OFTEN EQUIPPED WITH BRIGHT LED STROBES, ANTI-COLLISION BEACONS, OR NAVIGATION LIGHTS, THE SUDDEN, BRILLIANT FLASH OF LIGHT AT A HIGH CLOSURE RATE STRONGLY SUGGESTED A COLLISION WITH AN ILLUMINATED, UNMANNED AERIAL SYSTEM RATHER THAN WILDLIFE.

THE FO ASKED IF THEY SHOULD DECLARE THE STRIKE. THE CAPTAIN SUBSEQUENTLY REPORTED THE INCIDENT TO NEW YORK CENTER. BECAUSE ALL ENGINE AND FLIGHT INSTRUMENTS SHOWED NO ABNORMAL INDICATIONS, THE CREW MADE THE DECISION TO CONTINUE TO THEIR DESTINATION.

THE FLIGHT PROCEEDED NORMALLY. LATER IN THE CRUISE PHASE, THE FO RECONSIDERED HIS INITIAL ASSESSMENT. HE REALIZED THAT BECAUSE THE AIRCRAFT WAS STILL BELOW 10,000 FEET AT THE TIME OF THE STRIKE, THEIR HIGH-INTENSITY LANDING LIGHTS HAD STILL BEEN ILLUMINATED. HE HYPOTHESIZED THAT THE "LIGHTS" HE SAW FLASHING JUST BEFORE IMPACT WERE LIKELY THE AIRCRAFT'S OWN POWERFUL LANDING LIGHTS REFLECTING SHARPLY OFF THE WINGS OR FEATHERS OF A BIRD, CREATING THE MOMENTARY ILLUSION OF A SELF-ILLUMINATED MECHANICAL OBJECT.

THE FLIGHT CONCLUDED WITH AN UNEVENTFUL LANDING IN FORT LAUDERDALE (FLL). THE FO'S REVISED THEORY WAS CONFIRMED DURING THE STANDARD POST-FLIGHT EXTERIOR INSPECTION WHEN HE DISCOVERED BLOOD ON THE AIRCRAFT, VERIFYING THAT THE IMPACT WAS INDEED A BIRD STRIKE. THE FLIGHT CREW THEN FORMALLY REPORTED THE INCIDENT TO MAINTENANCE.

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.