DCA11WA068

NTSB incident investigation · Bombardier BD-100-1A10 · Iqaluit, Canada · March 12, 2011

Incident · No injuriesForeign investigation
Date
March 12, 2011
Place
Iqaluit, Canada
Injuries
3 uninjured
Damage
Minor damage
Phase of flight
Landing
Aircraft
N818RCBombardier BD-100-1A10
Defining event
Landing-landing roll: Runway excursion
NTSB office
Major Investigations Division
Lead agency
Other
Parties
FAA
Case key
80744

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the incident.

On this page

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Factual narrative

On March 12, 2011, a Bombardier BD100, registration N818RC, operated by Tri Marine Logistics, departed the runway to the right while landing on runway 35 at Iqaluit Airport (CYFB), Iqaluit, Nunavut, Canada. The airplane stopped about 100 feet from the edge of the runway in a snow bank. Skid marks left by the nose wheels on the runway show incorrectly orientated nose gear. The flight originated in Long Beach Airport (Daugherty Field), Long Beach, California, and was making a fuel stop at CYFB enroute to Milan Linate Airport, Milan, Italy.The incident is being investigated by the Transportation Safety Board of Canada. In accordance with ICAO Annex 13, the NTSB has appointed a U.S. Accredited Representative as State of Registry.

Aircraft

Registration
N818RC
Reported as
Bombardier BD-100-1A10
Category
Airplane
Serial number
20165
Engines
Honeywell AS907-1-1A, 6,944 lbs thrust, turbo fanHoneywell AS907-1-1A, 6,944 lbs thrust, turbo fan
Damage
Minor damage
Flight
Business · Part 91
Operator
Tri Marine Logistics LLC
Registered owner
Tri Marine Logistics LLC
Airworthiness certificate
Standard, Normal
Departed
LGB · Long Beach, CA
Destination
CYFB · Iqaluit
Flight plan
Unknown
Airport
CYFB · Iqaluit Airport, runway 35

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.