# Accident 20111130027571A: Piper PA-44-180, Seattle, WA, November 30, 2011 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: November 30, 2011, 19:33 local time - Place: Seattle, WA - Airport: Boeing Field/King County International - Damage: Destroyed - Collision: Collision on the ground - Phase of flight: Takeoff: Rotation - Operating rules: Pilot school (Part 141) - Operator: LJES - Location: 47.5300° N, 122.3019° W: From the FAA - Nearby events: https://openairdocs.org/map.md?lat=47.5300&lon=-122.3019&mi=10 - Aircraft: N2163N, a cancelled registration (https://openairdocs.org/deregistered/N2163N-2012-03-13) (OpenAirDocs) - Registry model: Piper PA-44-180 (registry code 7104402, https://openairdocs.org/model/piper-pa-44-180) (OpenAirDocs) - Registry engine: Lycoming O&VO-360 series (registry code 41514, https://openairdocs.org/engine/lycoming-o-vo-360-series) (OpenAirDocs) - Reported make and model: PIPER PA-44-180 - Reported engine: LYCOMING (L) O-360-A1H6, (R) LO-360-A1H6 - People aboard: 2 - Fatal injuries: 0 - Other injuries: 2 - Pilot certificates: Commercial pilot, flight instructor - Pilot flight hours: 1,996 total, 517 in this make and model, 158 in the last 90 days - NTSB investigation: [NTSB WPR12LA051](https://openairdocs.org/ntsb/WPR12LA051) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20111130027571A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. ON NOVEMBER 30, 2011, AT 1933 PACIFIC STANDARD TIME, A PIPER PA-44-180, N2163N, REGISTERED TO AND OPERATED BY HILLSBORO AVIATION, HILLSBORO, OREGON, AS A TITLE 14 CODE OF FEDERAL REGULATIONS (CFR) PART 141 INSTRUCTIONAL FLIGHT LOST DIRECTIONAL CONTROL DURING TAKEOFF FROM RUNWAY 31R AT BOEING FIELD INTERNATIONAL AIRPORT, SEATTLE, WASHINGTON (BFI) AND CRASHED INTO AN AIRCRAFT, WHICH HAD BEEN SECURED AND PARKED ON AN ADJACENT RAMP AREA. BOTH AIRCRAFT WERE DESTROYED BY A POST CRASH FIRE. THE CERTIFIED FLIGHT INSTRUCTOR (CFI), AND THE PRIVATE PILOT WHO WAS RECEIVING INSTRUCTION IN THE PIPER PA-44-180 RECEIVED MINOR INJURIES. NIGHT VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME. THE PIPER PA-44-180 ORIGINATED FROM THE PORTLAND-HILLSBORO AIRPORT (HIO), HILLSBORO, OREGON, AT ABOUT 1510 PACIFIC STANDARD TIME, ON NOVEMBER 30, 2011. THE PURPOSE OF THE FLIGHT WAS DESCRIBED AS A CROSS COUNTRY TRAINING FLIGHT FOR THE PRIVATE PILOT WHO WAS RECEIVING INSTRUCTION FROM THE CERTIFIED FLIGHT INSTRUCTOR (CFI). AFTER ARRIVING AT THE BOEING FIELD AIRPORT AT ABOUT 1700 PACIFIC STANDARD TIME, THE PIPER PA-44-180 WAS SERVICED WITH 42.0 GALLONS OF 100LL FUEL. THE STUDENT AND INSTRUCTOR LEFT THE AIRPORT TO HAVE DINNER, AND RETURNED AT ABOUT 1900 PACIFIC STANDARD TIME TO BEGIN PREFLIGHT PREPARATIONS FOR THE RETURN FLIGHT TO THE PORTLAND-HILLSBORO AIRPORT, (HIO). DURING AN INTERVIEW WITH THE FEDERAL AVIATION ADMINISTRATION INSPECTOR-IN-CHARGE, THE FLIGHT INSTRUCTOR (CFI) ONBOARD THE PIPER PA-44-180 REPORTED THAT THE AIRCRAFT BEGAN TO YAW AND ROLL TO THE RIGHT IMMEDIATELY AFTER ROTATION AT SUCH A RATE THAT IT WAS NOT POSSIBLE TO REGAIN CONTROL OF THE AIRCRAFT. NO ENGINE ABNORMALITIES WERE NOTICED OR DETECTED DURING ENGINE STARTING, TAXI OR RUN-UP. EXAMINATION OF THE ACCIDENT SITE REVEALED THAT THE WRECKAGE OF THE TWO AIRPLANES WAS CONFINED TO A SMALL AREA LOCATED ADJACENT TO THE NORTH WEST CORNER OF THE MAIN TERMINAL BUILDING. THE PARKED AIRCRAFT, A PA-34-200T, WAS STRUCK BY THE RIGHT WING OF THE PA-44-180 AND WAS PUSHED SO THE NOSE ROTATED (ANTI-CLOCKWISE) 90 DEGREES TO THE EAST. THE PA-44-180 CAME TO A REST INVERTED, 10 FEET FROM THE PA-34-200T, TAIL POINTED EAST. ACCORDING TO WITNESSES AND SURVEILLANCE VIDEO, THE POST CRASH FIRE STARTED APPROXIMATELY 31 SECONDS FOLLOWING THE ACCIDENT. AIRPORT RESCUE FIRE FIGHTERS RESPONDED TO THE SCENE IMMEDIATELY. THE WRECKAGES OF BOTH AIRCRAFT WERE RECOVERED TO A SECURE FACILITY AWAITING FURTHER EXAMINATION. ## The NTSB's investigation of this event (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB WPR12LA051](https://openairdocs.org/ntsb/WPR12LA051), Dec 1, 2011: Piper PA-44-180 (N2163N), Seattle, WA, substantial damage. Probable cause: The flight instructor’s failure to maintain airplane control during a go-around. ## Other reports on N2163N (5) Matched to the same aircraft by N-number and date. - [Incident 20090423005149I](https://openairdocs.org/incident/20090423005149I), Apr 23, 2009: Piper PA44180 (N2163N), Portland, OR, Minor damage. (-23) Pilot and instructor were flying VOR a approach to Hillsboro. Gear was lowered and confirmed by the pilot and CFI separately, at the initial approach… - [Incident 20060215008239I](https://openairdocs.org/incident/20060215008239I), Feb 15, 2006: Piper PA44180 (N2163N), Mulino, OR, Minor damage. (-23) The aircraft landed at Mulino, Oregon (4S9), a few seconds after touch down the nose gear collapsed. The pilot said the gear down indicator indicated… - [Incident 20030218001729I](https://openairdocs.org/incident/20030218001729I), Feb 18, 2003: Piper PA44180 (N2163N), Portland, OR, Minor damage. (-23) The aircraft was in a closed pattern at hio with CFI and student on board. The student selected "gear down". The landing gear annunciators indicated… - [Incident 20000622035059I](https://openairdocs.org/incident/20000622035059I), Jun 22, 2000: Piper PA44180 (N2163N), Aurora, OR, Minor damage. (-23)Instructor [privacy data omitted] and multi-engine student [privacy data omitted] made a VFR approach to the Aurora State Airport (3S2) for a practice… - [Incident 19810728058199I](https://openairdocs.org/incident/19810728058199I), Jul 28, 1981: Piper PA44180 (N2163N), Raleigh, NC, Minor damage. Za rt engine oil leak landed. Found prop model HC-C2YP-2CLEUF leaking. Repaired. Pilot not instrument rated. 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.