SMAAC Forums
Welcome, Guest. Please login or register.
Did you miss your activation email?
July 16, 2019, 06:29:06 AM

Login with username, password and session length
Search:     Advanced search
445 Posts in 235 Topics by 3514 Members
Latest Member: MerissaMul
Home Help Search Login Register
+  SMAAC Forums
|-+  SMAAC NEWS BLOGS
| |-+  Autumn 2017 E-NewsLetter
| | |-+  MSP Safety Questions: Public Announcement
« previous next »
Pages: [1] Reply Send this topic Print
Author Topic: MSP Safety Questions: Public Announcement  (Read 1650 times)
Forum Manager
Administrator
Jr. Member
*****
Posts: 51

« on: April 03, 2014, 10:38:23 AM »
Reply with quote

SMAAC reviewed National Transportation Safety Board (NTSB)information recently made public about the July crash at San Francisco International Airport (SFO).
The topic "Accident Stories" was updated and message was pos6ted at Aviation Watch.  We received requested from other citizens' groups to raise questions more generally at the Federal level.  A message was sent to Minnesota's US Senators and several Minnesota US Representatives reporting our views, and similar messages were sent by the other groups.  A public announcement released later, same subject, including that the review was being shared with various Federal Agencies and the US Congress.

We found parallels with acknowledged concerns at MSP: 

Air crew training, related to flight automation and airport instrument landing systems" (ILS);

Lack of precautionary go-arounds (aborted landings or approachs), often due to airport-area congestion and schedules;

Over-reliance by airline pilots on navigation systems (GPS, RNAV, etc.) and flight automation systems (ILS, auto-pilots, etc.);

Ineffective altitude and proximity warning systems;

Limited attention to operational anomolies by airport air traffic controllers.



SMAA also noted that this NTSB investigation remains "Preliminary" after 8 months, and that the airliner manufacturer (Boeing) and avionics suppliers, the FAA, and SFO Airport are denying any liability.  The carrier, Asiana Airlines, has acknowledged that its aircrew in this case failed to abort the landing "in time to avpoid the crash."  However, Asiana and NTSB also noted that the SFO glide-slope indicator system was out-of-commission and off, that the auto-throttle mode indicator (HOLD) was ambiguous in context, and that the ground proximity alarm was tardy.

The public announcement text will be available on-line in a day or two, and a link added to this story.
It remains to be seen if our statement: "The FAA Safety (first?) and Efficiency (operations at minimum separations whenever possible) policy urgently needs revision." elicits any actions at all in Washington.
« Last Edit: April 03, 2014, 11:25:59 AM by Forum Manager » Logged
Pages: [1] Reply Send this topic Print 
« previous next »
 

Powered by MySQL Powered by PHP Powered by SMF 2.0 RC3 | SMF © 2006–2010, Simple Machines LLC Valid XHTML 1.0! Valid CSS!