A Dash 8-400 turboprop left Happy Valley-Goose Bay on Thursday, Nov. 12 bound for Deer Lake, lost a wheel shortly after takeoff, and diverted to St. John’s International Airport, where it landed safely at about 4:10 p.m. Newfoundland time. PAL Airlines Flight 411 carried passengers and crew who were all accounted for afterward, and no injuries were reported.
Read next on Morning Overview: A handful of car transmissions are so tough that mechanics say they almost never die
The detail that turned a routine diversion into a story is the aircraft’s recent past. On Oct. 30 a wheel came off the same airplane while it landed in Wabush, Labrador. Two wheel losses in 13 days on one airframe is the pattern Canada’s regulators, an aviation-management professor and the airline’s own maintenance staff are now working through, and none of them has yet named a cause.
Flight 411 and the Wabush wheel loss on Oct. 30
The Aircraft Rescue and Fire Fighting Working Group’s daily digest records the facts of Nov. 12 in short form: the aircraft had lost a wheel, and the airline says it is the same plane that lost one on an earlier flight. CBC News reported that the earlier loss happened as the Dash 8-400 touched down at Wabush, and its story on the second event ran under the observation that a wheel had been lost again, on the same plane, in less than two weeks.
The two events differ in phase of flight. The Oct. 30 wheel came off during landing at Wabush, while the Nov. 12 loss came shortly after takeoff from Goose Bay, so the wheel assembly failed in both directions of the flight cycle, once on the way down and once on the way up. Neither source describes the cause of either loss, and PAL has not said which part of the assembly was involved.
NTV reported that emergency crews responded as the aircraft arrived in St. John’s, the standard precaution when a flight reports a landing-gear problem. The crew completed the diversion and landed without injury, and every passenger and crew member was accounted for.
What PAL did with the aircraft and the rest of its Dash 8 fleet
PAL Airlines removed the aircraft from service after the second event and said it was completing another inspection, according to the report on the plane’s removal. The airline also said it is inspecting the wheel assemblies across the rest of its Dash 8-400 fleet, a step that widens the check from one tail number to every aircraft of the type it operates.
That fleet-wide inspection is the airline treating the possibility of a shared cause, such as a part, a procedure or a maintenance step, as open. It also means the answer, whenever it arrives, will tell regulators whether the problem sits with one repaired airframe or with the way the type is maintained.
John Gradek on repair and maintenance as the likely place to look
John Gradek, who teaches aviation management at McGill University, called a repeat wheel loss on one aircraft “disturbing” and unusual. He said he was not calling the event dangerous, because emergency procedures exist for it, but that a second loss on the same aircraft is not something normally seen.
Gradek said the repeat points toward the repair and maintenance process. Possible explanations he raised include a wheel that was not properly attached or not quality-checked before the aircraft flew again. He argued PAL will need to evaluate its maintenance practices seriously and added that because those processes are normally documented, establishing what happened should not be difficult. The useful question, he stressed, is why it happened, since that is what prevents a third one.
TSB and Transport Canada: how much scrutiny the events have drawn
Hugo Fontaine, a media relations coordinator at the Transportation Safety Board of Canada, said the board knows about both events but had not deployed investigators, according to CBC’s reporting on the board’s position. The Oct. 30 event was classified as a Class 5 occurrence, which the board describes as having little likelihood of identifying new safety lessons that will advance transportation safety. Under the board’s occurrence classification policy, a Class 5 event gets data gathering within about 60 days and no investigation report.
For Nov. 12, Fontaine said investigators were collecting information and were in contact with the airline, and that a global Microsoft outage had slowed the process. It was too early to say whether the event would be investigated. Flavio Nienow, a communications advisor at Transport Canada, said the department is working directly with the operator and will not hesitate to take appropriate action if safety or regulatory deficiencies are identified under the Canadian Aviation Regulations.
The open question is whether the TSB upgrades its handling now that the same aircraft has been involved twice. A second Class 5 label would leave the cause of a repeat wheel loss without a public report, and Gradek’s point that the maintenance records exist suggests the board or Transport Canada could answer it quickly if they choose to look.
This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.
More from Morning Overview
- The Justice Department asked courts to undo approvals for three offshore wind farms, one already making power
- Over 20 trillion gallons of rain fell on the Four Corners states and Nevada in two weeks
- 11 engines built to run well past 200,000 miles
- Two Kentucky residents died when a small plane crashed at Missouri’s Lake of the Ozarks, and the NTSB is investigating