# Incident 20101118055169I: Bombardier CL-600-2B19, Mnneapolis, MN, November 18, 2010

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: November 18, 2010, 10:33 local time
- Place: Mnneapolis, MN
- Airport: Msp International
- Damage: Substantial damage
- Phase of flight: Takeoff: Climb Out
- Operating rules: Air carrier (Part 121)
- Operator: SWIA
- Location: 44.9800° N, 93.2638° W: Placed by OpenAirDocs: center of Minneapolis, MN, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=44.9800&lon=-93.2638&mi=10
- Aircraft: N863AS, a cancelled registration (https://openairdocs.org/deregistered/N863AS-2023-01-25) (OpenAirDocs)
- Registry model: Bombardier CL-600-2B19 (registry code 1390008, https://openairdocs.org/model/bombardier-cl-600-2b19) (OpenAirDocs)
- Registry engine: GE CF34 series (registry code 30015, https://openairdocs.org/engine/ge-cf34-series) (OpenAirDocs)
- Reported make and model: BOMBARDIER CL-600-2B19
- Reported engine: GE CF34 SERIES
- People aboard: 0
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Airline transport
- Pilot flight hours: 10,070 total, 5,537 in this make and model, 91 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20101118055169I

## Narrative

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

ON CLIMB OUT FROM MSP AT 300 FEET AGL STRUCK A BIRD WITH RIGHT WING RESULTING IN WING LEADING EDGE DAMAGE. AIRCRAFT RETURNED AND LANDED. PILOT WAS WARNED OF BIRDS IN AREA BY ATIS. BIRD STRIKE FORM 5200-7 WAS SENT TO THE FSDO BY THE ROC.

## Other reports on N863AS (1)

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

- [Incident 20021103036619I](https://openairdocs.org/incident/20021103036619I), Nov 3, 2002: Cndair CL6002B19 (N863AS), Evansville, IN. (-23) On 11/03/02 asoa flight 4156 advised of smoke in the aft cabin after turning on the APU bleed air. Declared an emergency. The aircraft landed without…

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.