6 ms·

I was going by AirSafe reporting 0.00 for their FLE. However, due to the size of SouthWest, a single fatality throughout the history of the company probably doe

I was going by AirSafe reporting 0.00 for their FLE. However, due to the size of SouthWest, a single fatality throughout the history of the company probably does not change this number from zero. http://www.airsafe.com/airline.htm http://www.airsafe.com/airline.htm However, they may not have updated their site beyond the incident summary because Southwest is still listed as an airline with zero passenger fatalities. http://www.airsafe.com/airline.htm http://www.airsafe.com/airline.htm

geoelectric 7y ago
Weirdly, that page is listed as updated in 2019. Someone must have missed the SW one. The Southwest page does mention the 2018 incident and fatality, and was updated the day of the incident in fact. However, the incident isn't "numbered" as a fatal event--instead it has a UL bullet instead of an OL number, which looks like a mistake. On one hand, AFAIK the event wasn't SW's fault at all--they'd performed maintenance on the engine to standards. The fan blades failed due to a material fatigue issue, and happened to hit the engine cowl at its weakest spot and detached it. But I thought Airsafe still would've counted that as related to the operation of the plane, though, and the FLE for that flight would be like 0.007 (1/143) and still round up to 0.01. Since only flights with a fatality at all count for their calculation that'd be an overall FLE of the same.
- mindcrime 7y ago
  Yeah, I would think that it would still "count against" SW in that regard, even though it wasn't a "plane crash" or whatever.
sbuttgereit 7y ago
That site also uses the word "crash". The Southwest flight in question didn't crash, per se... it landed at an airport. So if they mean crash to really mean "incident", then their site would be wrong. If they meant something closer to "fell out of the sky"... well... they'd maybe be right, but misleading. Crash or incident, that person certainly had a bad day and probably didn't care much about how that was categorized.

geoelectric 7y ago

Weirdly, that page is listed as updated in 2019. Someone must have missed the SW one. The Southwest page does mention the 2018 incident and fatality, and was updated the day of the incident in fact. However, the incident isn't "numbered" as a fatal event--instead it has a UL bullet instead of an OL number, which looks like a mistake. On one hand, AFAIK the event wasn't SW's fault at all--they'd performed maintenance on the engine to standards. The fan blades failed due to a material fatigue issue, and happened to hit the engine cowl at its weakest spot and detached it. But I thought Airsafe still would've counted that as related to the operation of the plane, though, and the FLE for that flight would be like 0.007 (1/143) and still round up to 0.01. Since only flights with a fatality at all count for their calculation that'd be an overall FLE of the same.

mindcrime 7y ago
Yeah, I would think that it would still "count against" SW in that regard, even though it wasn't a "plane crash" or whatever.

sbuttgereit 7y ago

That site also uses the word "crash". The Southwest flight in question didn't crash, per se... it landed at an airport. So if they mean crash to really mean "incident", then their site would be wrong. If they meant something closer to "fell out of the sky"... well... they'd maybe be right, but misleading. Crash or incident, that person certainly had a bad day and probably didn't care much about how that was categorized.