# Incident 20111211029431I: Bombardier Inc BD-100-1A10, Seattle, WA, December 11, 2011 - Type: FAA incident report (Accident/Incident Data System), as reported - Date: December 11, 2011, 20:38 local time - Place: Seattle, WA - Airport: Boeing Field/King County International - Damage: Minor damage - Collision: Collision on the ground - Phase of flight: Ground/Ramp/Ma - Operating rules: General operating rules (Part 91) - Location: 47.5300° N, 122.3019° W: Placed by OpenAirDocs at BOEING FLD/KING COUNTY INTL (BFI), within about a mile (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=47.5300&lon=-122.3019&mi=10 - Aircraft: N54HA, registered now (https://openairdocs.org/aircraft/N54HA) (OpenAirDocs) - Registry model: Bombardier BD-100-1A10 (registry code 1390044, https://openairdocs.org/model/bombardier-bd-100-1a10) (OpenAirDocs) - Registry engine: Honeywell AS907-1-1A (registry code 33908, https://openairdocs.org/engine/honeywell-as907-1-1a) (OpenAirDocs) - Reported make and model: BOMBARDIER INC BD-100-1A10 - Reported engine: HONEYWELL AS907-1-1A - People aboard: 4 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Airline transport - Pilot flight hours: 15,901 total, 532 in this make and model, 70 in the last 90 days - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20111211029431I ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. ON DECEMBER 11, 2011, AT 2038 PACIFIC STANDARD TIME, A BOMBARDIER BD-100-1A10 (CHALLENGER 300), N54HA, REGISTERED TO AND OPERATED BY ORANGE HAWK EXPRESS, INC, KIRKLAND, WASHINGTON, AS A TITLE 14 CODE OF FEDERAL REGULATIONS (CFR) PART 91 FLIGHT COLLIDED WITH A PARKED GULFSTREAM G-550, CS-DKF, AS IT WAS BEING MARSHALED INTO PARKING BY RAMP PERSONNEL AT THE KING COUNTY INTERNATIONAL AIRPORT, BOEING FIELD, SEATTLE, WA. THERE WERE NO INJURIES. NIGHT VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME. THE BOMBARDIER BD-100-1A10 (CHALLENGER 300) ORIGINATED FROM THE LONG BEACH MUNICIPAL AIRPORT, (LGB), LONG BEACH, CALIFORNIA, AT APPROXIMATELY 1800 PACIFIC STANDARD TIME, ON DECEMBER 11, 2011. THE PURPOSE OF THE FLIGHT WAS DESCRIBED AS A PRIVATE TRANSPORT FLIGHT FOR THE OWNERS OF THE AIRCRAFT. IN A STATEMENT PROVIDED TO THE FEDERAL AVIATION ADMINISTRATION INSPECTOR-IN-CHARGE, THE PILOT IN COMMAND STATED THAT HE WAS MOVING THE AIRCRAFT WITH REFERENCE TO THE COMMANDS OF A MARSHALLER, WHO WAS POSITIONED AHEAD AND WAS DIRECTING THE PILOT IN COMMAND TO PULL AHEAD INTO A PARKING AREA WITH LIGHTED WANDS. THE PILOT IN COMMAND NOTED THE PRESENCE OF WING WALKER STANDING BY THE LEFT WING. THE PILOT IN COMMAND STOPPED AND SHUT DOWN THE AIRCRAFT AFTER A "BUMP" WAS FELT SIMILAR TO "ROLLING OVER A CHOCK". INSPECTION REVEALED THAT THE LEFT WING TIP HAD IMPACTED THE NOSE OF THE PARKED GULFSTREAM 550. IN A SEPARATE STATEMENT PROVIDED TO THE FEDERAL AVIATION ADMINISTRATION INSPECTOR-IN-CHARGE BY THE FIXED BASE OPERATOR, THE WING WALKER WHO WAS POSITIONED OFF THE LEFT WING OF THE BOMBARDIER BD-100-1A10 (CHALLENGER 300), ATTEMPTED TO SIGNAL THE LEAD MARSHALLER WITH HAND AND RADIO SIGNALS PRIOR TO IMPACT, BUT COULD NOT SUCCESSFULLY ESTABLISH COMMUNICATION IN TIME. THE LEAD MARSHALLER STATED THAT FROM HIS POSITION THE LEFT WING TIP HAD ALREADY CLEARED THE NOSE OF THE PARKED GULFSTREAM 550, AND HE HAD LOST SIGHT OF THE WING WALKER'S HANDS. THE WING WALKER WAS NOT USING LIGHTED WANDS. ONCE THE AIRCRAFT WERE SEPARATED, THEY WERE BOTH SECURED FOR FURTHER EXAMINATION AND MAINTENANCE ACTION. BOTH AIRCRAFT WERE VISUALLY EXAMINED THE FOLLOWING MORNING BY FEDERAL AVIATION ADMINISTRATION INSPECTORS. EXTENSIVE SCRAPING WAS OBSERVED ON THE LEFT LEADING EDGE TIP AND WINGLET OF THE BOMBARDIER BD-100-1A10 (CHALLENGER 300). THE RADOME OF THE GULFSTREAM 550 HAD BEEN FRACTURED AND A CRESCENT SHAPE GASH WAS NOTED ON THE FORWARD AND LEFT SIDE OF THE RADOME. THE RESUTS OF THE DAMAGE WERE COMMUNICATED TO THE NATIONAL TRANSPORTATION SAFETY BOARD, WHO DETERMINED THE EVENT CLASSIFICATION AS AN 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.