FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Bearskin Airlines Flight 311

10 Nov 2013 · Near Red Lake Airport, Ontario, Canada

Swearingen SA227-AC Metro III · Crashed on approach after engine failure

From Thunder Bay International Airport (YQT) to Winnipeg / James Armstrong Richardson International Airport (YWG)

Report a problem

Event

NTSB case
DCA14RA009
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Unknown · led by another country; figures from NTSB notifications
Event fatalities
5 · all aircraft and ground
Ground fatalities
Unknown
Occupants
7
Survivors
2
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
2
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Not recorded

Swearingen SA227-AC Metro III

Flight
JV311
Aircraft type
Swearingen SA227
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
C-FFZN
Onboard fatalities
5
Route
From Thunder Bay International Airport (YQT)To Winnipeg / James Armstrong Richardson International Airport (YWG)
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Not recorded
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · IFR final approach
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Unknown or undetermined
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft power plant
  • Personnel issues › Psychological
  • Aircraft › Aircraft oper/perf/capability

From the investigation findings the Wikipedia article reports, sorted into the NTSB's cause areas with AI assistance.

Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.

From the Wikipedia article

On 10 November 2013, a Swearingen SA227-AC Metro III operating as Bearskin Airlines Flight 311, a regional flight in Ontario, Canada, from Sioux Lookout Airport to Red Lake Airport, crashed just 800 metres from the runway of its destination airport killing five of the seven people on board. The cause of the accident was determined to be an engine failure, exacerbated by errors made by the crew, who were unable to identify the issue.

Flight

The aircraft was scheduled to fly from Thunder Bay, in Ontario, to Winnipeg, Manitoba with two stopovers in Sioux Lookout and Red Lake. The accident occurred on the Sioux Lookout-Red Lake leg of the flight. At 6:16 pm the aircraft was cleared to land on runway 26 at Red Lake, and at 6:27 the landing checklist was completed. Just one minute after the checklist, at about 500 feet above the ground, the crew reported an issue, that would be later identified as a failure of a first-stage turbine wheel blade in the left engine, but they weren't able to identify it. The crew declared an emergency, maximum power was applied to the engines, and the landing gear was retracted. The aircraft then suddenly rolled to the left and struck trees and hydro lines with its wing. The aircraft crashed near Ontario Highway 125 and caught fire. Of the seven occupants both crew members died along with three passengers, of the two survivors one suffered serious injuries, the other minor injuries. The two survivors left the wreckage of the aircraft before it was totally engulfed in flames. The fire was extinguished shortly after the crash by a local fire crew.

Investigation and cause

Investigation

The final report of the accident was published by the Transportation Safety Board of Canada one year and five months after the crash. The investigation found out that the engine failure was caused by a failure of a first-stage turbine wheel blade on the left engine, causing the aforementioned engine to suffer from a total loss of power. The crew's failure to identify the issue resulted in their inability to take the appropriate actions necessary to maintain control of the aircraft and perform a safe landing. The blade failure alongside the landing configuration of the aircraft resulted in it having a high drag and asymmetric state, so as the plane's speed reduced under the minimum control velocity the pilots lost control of the aircraft causing the crash. The recommendations that were issued were that the crew of Fairchild Swearingen Metroliners should pay attention to the aircraft's negative torque sensing system in case of an engine failure, in order to initiate an engine failure checklist in time, that borescope inspections and 450-hour fuel nozzle inspections should be done on this aircraft model to find in time eventual internal engine damage and to not re-install unserviceable fuel nozzles on this plane model.

Text from the Wikipedia article “Bearskin Airlines Flight 311” (revision 1364275517, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article

NTSB narrative

The Transportation Safety Board of Canada (TSB) has notified the NTSB of an accident involving a Swearingen SA227 that occurred on November 10, 2013. The NTSB has appointed a U.S. Accredited Representative to assist the TSB investigation under the provisions of ICAO Annex 13 as the State of Manufacturer and Design of the airplane.

All investigative information will be released by the TSB.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

Wikipedia article: Bearskin Airlines Flight 311
Article
Bearskin Airlines Flight 311
Revision
1364275517 · 2026-07-15 · retrieved 2026-09-18
Wikidata
Q16691095
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA14RA009
Event ID
20131111X23645
Case number
DCA14RA009
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
Record
Wikipedia article "Bearskin Airlines Flight 311" (page 78911173, revision 1364275517); merged with NTSB case DCA14RA009 (events / aircraft)
Date
Wikipedia infobox: date
Place and country
Wikipedia infobox: site
Map position
Wikipedia: Wikipedia article coordinates
Aircraft, operator and route
Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports); gaps and aircraft details from NTSB record DCA14RA009
Operation
airline flight number in the infobox
Fatalities
Wikipedia: Wikipedia infobox: aircraft fatalities
Ground fatalities
Wikipedia: not stated in the Wikipedia infobox
Summary
Wikipedia infobox: summary
Source notes (2)
  • One occurrence in two sources, merged: the Wikipedia article "Bearskin Airlines Flight 311" and NTSB case DCA14RA009, matched by the same aircraft registration and date. For this event outside the United States Wikipedia's values are used where the two differ; each value names its source.
  • Filled from the NTSB case API where the bulk record had no value: coordinates. Values present in the bulk record are kept.