Notice bibliographique
Résumé
Assistant Professor at UND Aerospace discusses the story of an aircraft emergency landing on the Hudson River in 2009, now featured in a top box office motion picture \nNick Wilson, assistant professor of aviation at the University of North Dakota’s John D. Odegard School of Aerospace Sciences, has a unique connection to the emergency landing on the Hudson River of U.S. Airways Flight 1549 on Jan. 15, 2009.\nThe famous “landing” and courageous airline captain that made it happen are subjects of a major motion picture, “Sully,” currently No. 1 in the country, based on box-office returns.\nAs a systems and procedures instructor for the Airbus 320 (A320) — the aircraft flown by Airline Capt. Chesley Sullenberger — Wilson provided initial and continuing-qualification training for captains and first officers at a major airline for five years. Many of those aviators are still active crewmembers flying the A320 today.\nWilson remembers the incident well. He also recalls discussing assessments of the incident with his colleagues as they watched the story unfold on national television. \n“Whenever an incident or accident occurs,” Wilson says, “it’s really important not to make initial assessments without more detail. That’s a common outcome with the media.”\nRare incident\nWilson says the National Transportation Safety Board and FAA took a long hard look at the checklists and procedures associated with the incident.\nOne of the aspects that made this incident so unique was the dual-engine failure, which, at such low altitudes, is extremely uncommon. Because of the rarity, checklists associated with a dual-engine failures were not optimized, specifically procedures associated with “ditching” the aircraft.\nThe importance of including low-altitude engine failures in checklists is apparent when one considers the lack of safe places to force land an aircraft in heavily congested cities like New York City.\nSeeing 'Sully'\nThough Wilson has not been able to see “Sully” yet, he is looking forward to the opportunity. He’s eager to see how much detail of the incident the filmmakers covered.\nWhen speaking to people who aren’t pilots, Wilson offers advice on how to best enjoy the film:\n“One thing I would say to the general public watching the movie would be – ‘Take in as much of this experience as you can, because it certainly is going to be exciting,’” Wilson said. “’but also, research the topic in more detail. What I can’t comment on is how accurate the movie is compared to the realities that the flight crew faced. I’m certain they made an attempt to realize that and that’s the difference between making a movie and actually facing an emergency.’”\nJudgment call\nFlight 1549, piloted by Sullenberger, departed LaGuardia Airport in New York City just before 3:30 p.m. After climbing to 3,000 feet, the aircraft struck a flock of Canada geese, which caused damage to its engines and resulted in a loss of thrust for both.\nSullenberger opted to land in the nearby Hudson River after judging that he could not return to LaGuardia or any other airport. Through quick decision-making, Sullenberger and crew were able to safely guide the aircraft on to the Hudson with no loss of life.\nWilson commends Sullenberger on his decision.\n“The captain elected, and arguably very rightly so, to land in the Hudson where there would be the least potential loss of life, and it ultimately resulted in no loss of life, which is quite amazing,” Wilson said.\nInterestingly, the A320 involved in the Hudson River landing was equipped to handle an over-water landing. At the time of the incident, this was not common with the entire U.S. Airways fleet nor the fleets of many other major air carriers. This equipment was not a requirement for the route of Flight 1549, however, having passenger life vests and escape rafts on board ended up being advantageous in the rescue effort.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction distillée sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,000 | 0,000 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,000 | 0,000 |
| Bibliométrie | 0,000 | 0,001 |
| Études des sciences et des technologies | 0,000 | 0,000 |
| Communication savante | 0,000 | 0,001 |
| Science ouverte | 0,000 | 0,000 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,000 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule tête enseignante, pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».