Monday, January 25, 2010
January 25 - An Ethiopian Airlines 737 crashed in the Mediterranean Sea shortly after takeoff from Beirut, killing all 97 aboard. Thunderstorms were reported in the area at the time of the crash.
January 24 - A Taban Air Tupolev TU-154 caught fire while making an emergency landing in Mashhad, Iran, injuring 42 of 157 aboard. The aircraft was reportedly landing in heavy fog when its tail and one wing struck the runway.
January 23 - A United Airlines flight bound for Las Vegas from Washington D.C. made an emergency landing in Denver after a passenger attempted to open an emergency exit during the flight. Passengers reportedly restrained the man after the incident.
January 23 - Both aboard a Piper Aerostar were killed after crashing near Sugar Grove, Illinois. The aircraft had reportedly just departed Aurora Municipal Airport before the crash.
January 23 - A U.S. Navy T-34 attached to Whiting Field Naval Air Station in Florida crashed into Lake Pontchartrain on approach to New Orleans, injuring one pilot and leaving the other missing and presumed dead. The aircraft was on a training flight at the time of the crash.
January 23 - Both aboard a Tecnam P-2002 were killed after crashing near Waxahachie, Texas. The aircraft was reportedly operating on behalf of a local high school aviation training program at the time of the crash. Light rain was reported at the time of the crash.
January 22 - The pilot of a crop-dusting helicopter was uninjured after clipping power lines and crash-landing near Shafter, California. The pilot reported having engine trouble before the crash.
January 22 - An ACE Air Cargo Beech 1900 crashed in the sea off Sand Point, Alaska, leaving both aboard missing and presumed dead. The flight had reportedly just departed Sand Point en route to Anchorage at the time of the crash. AVSIG Discussion
January 22 - A news traffic helicopter safely autorotated to a landing in Farmington Hills, Michigan after the engine caught fire and quit. AVSIG Discussion
January 22 - A Turkish SunExpress flight en route to Turkey from Germany made a safe emergency landing in Thessaloniki, Greece after the captain received a bomb threat on his mobile phone during the flight. The aircraft was searched in Greece. No bomb was found.
January 22 - A United Airlines 757 made a safe return to Washington-Dulles International Airport in Virginia after ingesting a large bird into the right engine shortly after takeoff.
January 21 - Both aboard a Finnish Air Force F-18 safely ejected before the aircraft crashed near Juupajoki, Finland. The aircraft was on a training flight at the time of the crash.
January 21 - The pilot of a Piper Aztec called the U.S. Coast Guard on his satellite phone from his life raft after crashing in The Bahamas. The pilot was reportedly rescued by the crew of a nearby boat.
January 21 - A coast guard helicopter crashed in the sea off Almería, Spain, killing three and seriously injuring one. The flight had been dispatched to search for the source of signal flares out on the water at the time of the crash.
January 21 - A USAir flight operated by Chautauqua Airlines made an emergency landing in Philadelphia during a scheduled New York-Louisville flight after passengers and crew became concerned about a passenger with a "religious device" strapped to his head. The aircraft was met by law enforcement at a remote location at the airport. The "religious device" was determined harmless.
Copyright 2010 www.AVSIG.com
Tuesday, January 19, 2010
January 18 - The pilot of a 1947 Luscombe 8-A was injured after crashing into a hangar at Springfield/Robertson County Airport in Tennessee. The aircraft reportedly bounced hard on landing before crashing into the hangar.
January 18 - A Cessna 172 bound for Palm Springs International Airport crashed in Joshua Tree National Park, injuring both aboard. Heavy rain was reported at the time of the crash.
January 18 - The pilot of a Robinson R22 was uninjured after crashing near Rockhampton in Queensland, Australia. The aircraft reportedly experienced a tail rotor failure before the crash.
January 18 - A Dallas-San Francisco American Airlines MD-80 made a safe emergency landing in San Jose after experiencing trouble with the aircraft's throttle. Passengers were deplaned and bussed to San Francisco.
January 18 - All four aboard Mitsubishi MU-2 registered to Mitts Corporation of Gainsville, Florida were killed after crashing on approach to Lorain County Regional Airport.
January 18 - A Beechcraft Duke crashed into a residential area near Madison, Alabama, killing both aboard. The pilot was attempting to return to Huntsville International Airport after experiencing engine trouble at the time of the crash. The aircraft crashed into an empty lot between two houses. No injuries were reported on the ground.
January 17 - A single-engine plane made a forced landing in a field near Cedar Rapids, Iowa, injuring the pilot. The pilot reported low fuel before the incident. Heavy fog was present in the area at the time.
January 17 - A single-engine Cessna registered to the U.S. Department of the Interior crashed in a heavily-wooded area near Corvallis, Oregon, killing both aboard. The flight was engaged in a count of migratory birds at the time of the crash.
January 17 - A Cessna 172 crashed near Grand Rapids Michigan, killing both aboard. Low cloud cover was reported at the time of the crash.
January 17 - All three aboard a single-engine Piper were killed after crashing off Bimini Bay Resort in the Bahamas. The flight was reportedly en route to Fort Lauderdale, Florida from New Providence at the time of the crash.
January 16 - Terminal 8 at JFK International Airport in New York was evacuated after an unauthorized person opened a door restricted to airline employees, activating an alarm. Several planes of boarded passengers were also evacuated and rescreened.
January 16 - No injuries were reported after an Iran Air jet rolled off a runway end at low speed in Stockholm. Passengers exited the aircraft via roll-up stairs.
January 16 - A United Airlines flight bound for Sydney, Australia from Los Angeles made an emergency landing in Brisbane due to low fuel.
January 15 - Both aboard a Piper Navajo were killed after crashing near Oxford, UK. A witness reported hearing an engine quit before the crash.
January 15 - A scheduled Minneapolis-Atlanta Delta Airlines flight made an emergency landing in Indianapolis after an engine failed. The 737 landed safely.
January 15 - A Vans RV-4 crashed near Bay St. Louis, Mississippi, killing both aboard. Witnesses reported seeing the aircraft invert before the crash.
January 15 - A JetBlue flight bound for Chicago from New York made an emergency landing in Buffalo. The aircraft reportedly lost cabin pressure during flight.
January 15 - A Piper PA-18 registered to Smoketown Banners LLC made an emergency landing in the Fresh Kills Landfill on Staten Island after experiencing engine trouble. The aircraft was towing a banner commemorating the 2009 Hudson River landing of USAir Flight 1549 at the time of the incident.
January 14 - Flight operations at IGI Airport in New Delhi were disrupted for over two hours after air traffic control flight navigation software failed during an upgrade attempt. Flights were manually handled during this period.
January 14 - A United Airlines flight bound for Sydney, Australia from San Francisco made an emergency landing in Brisbane due to low fuel.
January 14 - An American Eagle jet made an emergency landing at Springfield-Branson National Airport in Missouri for undisclosed reasons. The aircraft landed without further incident.
January 14 - A single-engine plane owned by Gospel Ministries, Incorporated crashed after clipping trees on takeoff from Collegedale Airport in Tennessee. The pilot was able to exit the aircraft safely before it caught fire.
January 14 - An ultralight crashed near Port Manatee, Florida, killing the pilot. The crash reportedly occurred on takeoff from a nearby airport.
January 14 - The pilot of a Cessna Caravan operated by the Kimberly Charter Company was uninjured after his plane flipped short of the runway while attempting an engine-out landing at Beagle Bay Airstrip in Broome, Western Australia, Australia. The pilot reported that his engine quit while flying over the Dampier Peninsula.
January 14 - The pilot of a Royal New Zealand Air Force CT-4 Trainer was killed after crashing near Bulls, New Zealand. The aircraft was reportedly engaged in training maneuvers in support of the Red Checkers display team at the time of the crash.
Copyright 2010 www.AVSIG.com
Wednesday, January 13, 2010
Just a decade ago we were letting absolutely anybody into the departure gate areas of U.S. airports – passengers, their fond-goodbye well-wishers, random airplane gawkers, homeless people looking for a warm floor – so long as they successfully passed through a security checkpoint staffed by people who were often less vigilant than Wal-Mart “greeters.”
Set off the metal detector?
Must be the steel shank in your boots. Go ahead and get on the airplane anyway. Let’s keep the line moving.
Today you can forget about wearing steel-shanked boots or any footwear at all through airport security. If “the system worked as it was supposed to” your name has already been checked against several passenger watch lists ... probably within seconds of purchasing your ticket. You’re not bringing Aunt Dot through the terminal to see you off, and you’re not getting past anybody with that four-ounce bottle of dandruff shampoo.
Smart airline security, like smart security of any kind, will always entail the best vigilance against known threats and intelligent monitoring of new threat forms. The developed world has gotten the message, and the system and tools are in place.
But what are we doing with them?
When Umar Farouk Abdul Mutallab attempted to blow up Northwest Flight 253 over Detroit in December, reaction in the U.S. was sadly familiar: posturing blowhards pinning the blame on the U.S. president (as if President Bush was going to stand up and swat hijacked airliners out of the sky in preference to finishing his visit with school children on September 11 ... as if President Obama was going to drop his golf clubs in Hawaii to go help inspect underwear at airport security checkpoints) and the introduction of a new administrative euphemism in the air travel world:
An Abundance of Caution.
“An Abundance of Caution” is a the new buzz phrase that means, “Sorry this looks ridiculous, but it’s important that we look like we’re doing security work, even if it isn’t the security work we’re supposed to be doing.”
It’s a phrase to describe scattered knee-jerk new airline security measures that look to be the work of a collective brain trust channeling inept school administrators from 1980s teen angst films.
In the case of the Northwest flight and more recently in the evacuation and re-scan of a terminal full of passengers at Newark International Airport, we had the tools in-place to eliminate the risks, but failed to use them.
While installing body scanners at all airports might be the ideal way to detect clothing-borne explosives, acting on information ... say information like a formal report, logged in a government security database, which states a passenger you’re screening has ties to al-Qaeda ... might be useful in the absence of the tech gee-wizardry. You might want to pull the guy aside for a closer look-see, and you might want to do it free from post-office-level rules-of-engagement.
Should we really be maintaining a list of potential terrorists who don’t warrant extra scrutiny at an airport security checkpoint?
At Newark, one TSA employee reportedly failed to monitor the “sterile” arriving passenger egress zone in Terminal C for several minutes, allowing one man to walk completely past screening and into the gate area.
All those impressive badges and machines on the screening side of security checkpoints look pretty silly when someone can waltz right through the gaping nobody’s-minding-the-store side of the setup and disappear into the crowd.
In aviation safety there are rarely “new” accidents – most result from failures to adhere to established safety practices. Aviation security is different only because the threat is actively and always engaged in trying to overcome the system.
The first question to ask after a system breach in any discipline is whether or not the breach occurred because of a breakdown in the system or because a novel intrusion has beaten the system. If the former, the decision tree says find out what broke and fix it ... not create new and distracting processes.
Our recent record in U.S. air security has not been good, with two high-profile cases of the Transportation Security Administration failing its job, and in response, inane ramped-up Abundance-of-Caution security intercepts – where six-year-olds are having their Play Doh confiscated and we scramble F-16s when a nutjob rambles about crashing on Gilligan's Island (most tragically without the classic choice of Ginger or Mary Ann – only Mrs. Howell) on the passenger comment card.
It goes without saying ... but we like to say it here anyway ... that U.S. airline safety would be better served by dropping these brain-dead “Abundance of Caution” stunts in favor of an abundance of competence in performing existing passenger screening processes, and an abundance of common sense in responding to all potential security threats.
Monday, January 11, 2010
January 10 - A Piper Navajo crashed into a mountainside in heavy cloud cover east of Honolulu, killing both aboard. Witnesses said they heard the aircraft's engine making a loud popping noise before the crash.
January 10 - Flights were canceled at Cleveland Hopkins International Airport in Ohio after a power failure at the airport. Road salt dust driven by strong winds is suspected to have contributed to a transformer fire before the outage.
January 10 - A United Airlines Airbus A-310 made a safe emergency landing at Newark International Airport after the right landing gear failed to extend. The aircraft made a smooth landing on the nose and left gear. Passengers evacuated via emergency slides without incident. AVSIG Discussion.
January 9 - No injuries were reported after a single-engine plane crashed off the south coast of Long Island. The pilot and passenger were able to walk to shore safely from the crash site.
January 9 - A Cessna 140 crashed west of Chico Airport in Chico, California. No injuries were reported.
January 10 - All four aboard a single-engine Piper received minor injuries after crashing near Mittagong, Australia. The aircraft reportedly clipped trees shortly after taking off from a nearby airport.
January 9 - A single-engine plane crash-landed on a beach near Durban, New Zealand, injuring one of four aboard. The aircraft's propeller reportedly disintegrated before the crash.
January 9 - An Airborne Streak 2 ultralight crashed near Bakersfield, California, killing both aboard. The pilot and passenger reportedly jumped from the aircraft before the crash.
January 8 - No injuries were reported after a Piper Navajo with 14 aboard made an inadvertent gear-up landing in Bloodvein, Manitoba. The aircraft was operating by Superior Airways as a commercial airline flight at the time of the accident.
January 8 - A Great Lakes Beech 1900 made an emergency landing at Ernest A. Love Field in Prescott, Arizona after the aircraft's nose-gear failed to lower. The flight circled the airport while the gear was lowered manually. The aircraft landed without further incident.
January 8 - An AirTran Airways 737 bound for San Francisco from Atlanta made an unscheduled landing in Colorado Springs after a passenger locked himself in a lavatory and refused to comply with the instructions of the flight crew. Two F-16s escorted the flight to the airport. Passengers were deplaned in Colorado Springs without further incident.
January 8 - A Delta Connection Embraer 145 aborted takeoff from Logan International Airport in Boston after a smoke odor was detected in the cabin. The flight was evacuated using rolling steps. No injuries were reported.
January 8 - A single-engine plane crashed at Sequim Valley Airport in Sequim, Washington, killing the pilot. The aircraft reportedly crashed at high speed nose-first into a field adjacent to the airport.
January 6 - A helicopter owned by Chesapeake Bay Helicopters crashed near Grantsville, Maryland, seriously injuring the pilot.
January 6 - A passenger was removed from a Detroit-bound Delta Airlines flight in Miami after he reportedly made loud anti-Semitic comments during taxi. Authorities tasered the man after he struggled an arresting officer.
January 6 - Two F-15 fighter jets escorted a Hawaiian Airlines flight back to Portland International Airport in Oregon after a passenger reportedly made provocative comments and refused to stow his carry-on bag. The flight landed without further incident and the passenger was removed from the plane.
January 6 - A Cessna 172 skidded off the runway and flipped during a landing attempt at Ramona Airport in California, slightly injuring the student pilot. The pilot was reportedly returning from a solo flight at the time of the crash.
Copyright 2010 www.AVSIG.com
Wednesday, January 6, 2010
[Accidents & Incidents published by www.AVSIG.com are preliminary and not meant to reflect the complete or official record of aviation accidents/incidents and their causes.]
January 5 - A would-be passenger was detained in Stuttgart, Germany after he repeatedly told security personnel at the airport that he had explosives sewn into his underwear. After later claiming he was only joking, security screeners performed a full body search and no explosives were found. The man and his family were denied boarding. The airline reported that no refund would given, and authorities were considering imposing several fines against the man.
January 5 - All four aboard a Bell 206 helicopter being operated by the California Department of Fish and Game were killed after crashing near Redinger Lake near Fresno, California. The aircraft reportedly struck power lines before the crash.
January 5 - A Learjet operated by Royal Air Charter crashed in a wooded area while attempting to land at Chicago Executive Airport in Wheeling, Illinois, killing both aboard. The aircraft was reportedly operating as a cargo flight at the time of the crash.
January 5 - A terminal at Minneapolis-St. Paul International Airport was evacuated after a bomb-sniffing dog reacted to a piece of luggage on a baggage carousel. The suspicious bag was searched, but no bomb was found.
January - 5 A Royal Jordanian Airbus A-340 made an emergency landing in Shannon, Ireland during a Montreal-Amman flight after a passenger complained of chest pains. The passenger was safely evacuated to emergency personnel and the flight continued after a four-hour delay.
January 4 - A Ryanair 737 returned to Liverpool John Lennon Airport after a cockpit warning light indicated an onboard fire. All passengers and crew were safely evacuated via emergency slides; no sign of fire was immediately found by investigators.
January 4 - The pilot of a Cessna 172 was killed after crashing north of Bangor, Maine. The pilot reported ice on the aircraft's wings prior to the crash,
January 3 - A Russian Orenburg Airlines Boeing 737 made a forced landing in Iran after developing unspecified trouble during a scheduled flight from Perm to Dubai. The aircraft landed without further incident.
January 3 - A single-engine Cessna crashed shortly after takeoff from Doylestown, Pennsylvania, but the pilot and passenger escaped the aircraft without injury. The aircraft reportedly lost power before the crash.
January 3 - Terminal C at Newark International Airport in New Jersey was locked down after a man walked past screeners via the outbound exit from the secure area. Officials were reviewing video from the security checkpoint.
January 3 - No injuries were reported after an Air Berlin 737 ran off the runway during an aborted takeoff in Dortmund, Germany. The crew reportedly elected to abort takeoff after the pilot and co-pilot received contradictory speed information on their instrument displays.
January 2 - A passenger unwittingly carried RDX plastic explosives aboard a Danube Wings flight bound for Dublin after Slovakian security personnel at Poprad-Tatry Airport in central Slovakia placed bomb components in his luggage as part of a security test. Security officials reportedly placed explosives in nine randomly selected pieces of passenger luggage at the airport as part of the test. Eight bags were detected by screeners.
January 2 - A single-engine Cessna crashed in Ursel Belgium, killing both aboard. The pilot reportedly aborted a landing attempt in heavy snow before the crash.
January 2 - A Delta Airlines flight bound for New York returned to Boston after the cockpit crew smelled smoke. The flight landed without incident; the source of the smoke odor was not immediately found.
January 2 - A Fairchild Metro III operated by Locair, Inc. veered off the runway and struck a fence during landing at Lake Cumberland Regional Airport in Somerset, Kentucky. No injuries were reported in the crash, which reportedly occurred after the aircraft's nose-gear steering malfunctioned.
Copyright 2010 www.AVSIG.com
Monday, January 4, 2010
(The following are pull-quotes from forum discussion in the Accident & Incident section of AVSIG. Direct links below each discussion).
Air France 447 Discussion (Airbus A330, June 1, 2009)
Conflicting reports on whether the aircraft was within radar coverage.
Speculation is on lightning but with very few exceptions lightning does not bring down airplanes.
Reports of electrical problems. The FBW AB can be flown WITH ALL electrical gone. Not easy but you have the trimmable horizontal stabiliser, rudder and the engines have the FADECs.
On average, almost all airliners are struck at least once a year by lightning.
To be certified the airplane has to be able to take strikes. The equipment (electrical avionics, etc) are put in a 'hardened' location to prevent the lightning from eating the systems.
Systems on most modern jets are self-monitoring and self-reporting so it is likely the -330, when some systems failed, would have made the report without requiring pilot input.
Good summary about lightning and aircraft being able to continue flight with loss of electrical. Like you said, lightning strikes are somewhat rare (I can recall about 5 strikes between my navy and Northwest -and yes, we did keep on flying OK with the loss of some minor systems in 3 cases).
Of course it's way too soon to know much about this accident -except to note that the aircraft is obviously down and all on board likely killed. The A330 has up to now had a very good safety record.
The CVR and DFDR units do have sonar signals under water, but they are not very strong and I believe takes special receivers, etc. to even find the signals.
I don't think anything can be ruled out at this early stage, including a possible bomb?
Tragic for sure and I'm doubtful if there are survivors.
I am wondering about the depth at that point in the Atlantic. It is not going to be easy to retrieve the CVR and FDR.
I'm a little surprised that the reports seem to have no real idea where the AC went down. The first report I read (NYT) said they were lost from the radar screen. Now reports are talking about the Cape Verdes. I don't understand why the position reports from the flight can't pin down the location better. Unless, they went NORAD from a lightning strike. Sadly, I too hold little hope for the pax and crew.
I don't think the surveillance in the South Atlantic is all that great. That was kinda the point of the SURTASS ships, and there are only a few of them still in operation. In fact, I understand that the whole network ain't what it used to be.
I know that supposedly the [i]Scorpion[/i] casualty was picked up but that was both a lot further north and (I suspect) a lot more energetic than the impact of an A330 would be.
The depths out there are abyssal so any search and recovery operation will be a heck of a challenge.
So far it sounds like non-radar, with a missed oceanic position report being the first ATC clue - which is why exact location is not available. Still pretty sketchy data, though.
The plane ran into strong turbulence at 4 a.m. Paris time and sent automatic distress signals at 4:14 a.m., the company said. The flight sent 10 distress messages shortly before it disappeared, signaling an “unexpected and exceptional incident aboard,” Gourgeon said, without giving more details.
No further contact isn't good. Sounds like there was no Mayday on the radio for other flights which may have been in the area to pick up. No contact after lifeboats would normally have been employed which contain ELTs.
Once radar service is terminated, about how often would the aircraft be making position reports? I remember John Deakin talking about every 30 minutes.
It's been a while but if my memory is correct, position reports are made very 10 deg. with the time not to exceed 60 minutes which would require additional reports. I don't recall ever in my many Atlantic and Pacific crossing ever exceeding the time. Airspace rules have changed considerably since I retired.
If the aircraft had an Automatic Dependent Surveillance - Contract (ADS-C) contract set up then normally a report is made every 20 - 30 minutes and at any reporting point on the ocean track with more frequent reports for track offsets and for 'events' like deviations. Each oceanic airspace authority may set its own reporting period as part of the 'contract' set up when the aircraft connects on data-link. (WATRS is every 20 minutes; Japan every 1600 seconds). The aircraft could also have ADS contracts with the next oceanic airspace and with its own AOC.
The reason for the extended period between ADS-C reports appears to be save money on the number of SATCOM transmissions made during a flight. I have been involved with experiments with ADS updates every half-second so the slow update rate is not due to a technical issue.
Re the debris spread, I just caught an interesting tidbit in Hamburger Abendblatt. The paper quotes an Air France spokesperson as saying there were multiple malfunction reports from the automated maintenance equipment over a period of three minutes.
If it was a breakup which took place over roughly three minutes, a 30 mile debris spread would seem reasonable.
Think back to the famous "pop-top" Hawaiian Air flight. The initial event certainly left debris and likely caused some systems (if only cabin lights and enterainment, maybe more) to malfunction. If the structure had continued to break up from there, the whole process could have gone on over a considerable distance. As it really was, I suspect various bits blew off for a while after the initial event.
Could this be another composite rudder loss, either due to overstress or a lightning strike? I assume the composites used on commercial airliners have an aluminum grid embedded in the skin for lightning protection. Or maybe that's not necessary on carbon fiber composite, I don't know.
Yes, the rudder (vertical tail loss) is one of about 100 possibilities at this point.
They were in or close to a lot of towering thunderstorms, which is the norm this time of year at that location.
It seems like the aircraft did break apart in the air -at least from the initial reports of possible parts noted on the ocean surfact. (and some fires noted by an aircraft behind them on about the same route). So far it's only been looked at from the air as far as I know at this point.
I don't understand the almost 3-4 minute series of ACARS messages. It seems like they should have been closer together.
The clock is indeed ticking on finding the DFDR and CVR boxes.
It would be amazing if they actually get the black (well they are orange) boxes back within the next 21-30 days that they will be (in theory) pinging.
I assume that a possible bomb idea is still on the table -although it seems to be mostly dismissed in most reports I've noted.
Regards, and I have the start of a worry that we may never know the causes. Hope I'm wrong about that concern
New information provided by sources within Air France suggests, that the ACARS messages of system failures started to arrive at 02:10Z indicating, that the autopilot had disengaged and the fly by wire system had changed to alternate law. Between 02:11Z and 02:13Z a flurry of messages regarding ADIRU and ISIS faults arrived, at 02:13Z PRIM 1 and SEC 1 faults were indicated, at 02:14Z the last message received was an advisory regarding cabin vertical speed. That sequence of messages could not be independently verified.
This from the Aviation Herald, esp. the third paragraph quoted below:
Air France reported, that they had received an automatic message from the
airplane reporting an electrical short circuit and the failure of multiple
systems at 02:14Z. Air Traffic Control as well as Military Stations along the
Atlantic coast of South America, Africa, Portugal, Spain and France have been
alerted and attempted to contact the airplane without success. Attempts to
locate the airplane using civil and military radars from both west and east
coasts (including France) of the Atlantic also proved unsuccessful. The
airplane entered service in 2005 and had accumulated 18870 flights hours. The
captain had 11700 flight hours, one of the first officers had 3000, the other
6600 flight hours.
Sources within Air France reported, that the automatic message did not only
report an electrical short circuit, but also the loss of cabin pressure. This
information has been confirmed by FAB, who also stated, that the position of
the airplane was given as N3.5777 W30.3744 in that message.
New information provided by sources within Air France suggests, that the
ACARS messages of system failures started to arrive at 02:10Z indicating,
that the autopilot had disengaged and the fly by wire system had changed to
alternate law. Between 02:11Z and 02:13Z a flurry of messages regarding ADIRU
and ISIS faults arrived, at 02:13Z PRIM 1 and SEC 1 faults were indicated, at
02:14Z the last message received was an advisory regarding cabin vertical
speed. That sequence of messages could not be independently verified.
Would you (or anybody) mind 'splaining what ADIRU and ISIS mean to this Cessna pilot?
The ADIRU of which there are three provides the pilot with airspeed, altitude and position.
The ISIS in the Integrated Standby Instrument System, the backup.
Lose ADIRU 1 and you will probably (not sure) have the autopilot disconnect. The PRIM1 and SEC1 are flight control computers again where there are 3. Lose some of these computers and the flight control laws may change from NORMAL to ALTERNATE. Again, not sure..
The Laws are NORMAL, ALTERNATE and DIRECT. With all laws gone you have a trimmable horizontal stabilizer, rudder and engines... very basic.
[Why not stream systems data?] You can access the net from an aircraft, no excuse whatsoever that at least partial *critical* flight data isn't streamed. Technical reality.
That said, I'd hope folks here know where I stand as regards privacy (oh, in favor of it ;-)), and my respect for those that fly self-loading cargo types like myself. This accident just makes the point that the current system doesn't work, the technology exists to get around it a bit, be interesting to see the results this time as regards the tombstone mentality. My $0.02...
Flight data recorders exist due to regulation.
Who is going to pay for the streaming of data? What's the benefit to payee?
I don't see anything changing until regulations change.
The passenger pays, just like they do now for being able to stream their data on flights where that's available. This cost issue doesn't particularly fly for me ;-) Spread the cost around among *all* required-to-be FDR equipped passenger aircraft.
I don't know how many parameters the 330 currently records, best I can tell it's a minimum of 280 and may range upwards to 1200 (?). Regardless, compressed, I can't see how that would be anything but a minimal load, even streamed real-time, compared to one pax sending video or similar large files as Reams mentioned. As regards reliability, well, the FDR would still be there too, and the thought process that streaming the data would have to be perfect outa the box doesn't play. Call it a non-critical/experimental system, whatever, but get it started. Something tells me that if I can stream live video from my apartment, this isn't a technical challenge that's out of the reach of Airbus, Boeing, and the avionics designers. Which is obvious, given that they were getting messages from the aircraft when certain fail modes occurred. So, write some new code to parse incoming real-time data to anticipate upcoming potential failures, also not an impossible task, as demonstrated by the FBW systems themselves.
Ask Airbus, Air France and the avionics manufacturers what the benefit may be if the current rumor that faulty airspeed indicators/indications may have directly contributed to the accident. Let's start with number of family members * large sums of money per. Penny-wise, pound-foolish mate, the FAA doesn't have a lock on the tombstone mentality.
I believe the regulatory issue was addressed elsewhere, so, they pass a new reg.
Maybe... To the extent that maintenance items might be valuable, seems that such data is already provided in periodic bursts. So, users will have to either see a value proposition in it for them, or have "forced cost" added by government that is tacked on to fares.
As to CVRs, such data could be easily encrypted, to be unencrypted only in event of accident investigation....
I remember a flight several years ago where I was working on the internet sitting in my seat on an SAS machine while flying over the North Atlantic and Greenland, sending real time emails with large file attachments back and forth, using the Boeing Connexxion system (now defunct). So, the technology is available, but apparently the question is at what cost...
Reliability matters a lot, too. It needs to be sent in real time, or at least in some way that guarantees that the most recent data isn't lost - ever - over a comm link that works in remote areas, regardless of aircraft attitude, even when the aircraft may be doing some pretty strange things. I suspect that this isn't as simple as it may first seem. "Ooops - we seem to have missed the last minute of flight..." isn't real helpful.
Oh, I can see it now - "we pay for live streaming so your loved ones will know exactly how you died". Hmmmm, I think marketing it going to have a tough sell on that one.
Eventually, yes, they'd pay. But there's no advantage for an airline or airplane manufacture to voluntarily file that flight plan.
The only direct beneficiaries are the news media, the investigators, and the government that has to pay to retrieve the black box.
Howz 'bout future passengers and crews who don't have to crash (or disappear from the face of the Earth) thanks to lessons learned from that streamed info?
(There's probably some feel-good marketing in there somewhere).
I'm not denying there's public good to the idea. But the lessons learned are passed to all pilots of all airlines.
Any marketing campaign is going to have to be on a "feel good" type of thing so that the public is willing to pay a bit more for a favorite carrier. But usually anything that even suggests that flying might result in a crash sends most marketing types into a fit. ("Acme Airlines - We learn from our mistakes")
I still say it's easier to talk a congress critter into the idea than an accounts/MBA type.
The marketing reference is tongue-in-cheek, but I like your campaign tagline. IMO we are long overdue for remote voice/data telemetry. F447 has already proven the value on a small scale (the automated status messages are better than nothing), and I can't think of any reason more info couldn't be transmitted. Having to go hunt a little metal box in a smoking hole or 12,000-ft-deep ocean to get cockpit and flight control info in this day and age makes no sense to me.
Cost? Somebody convince me they'll have to cut out my .3 oz bag of in-flight pretzels to pay for it and I'll shut up :).
Well I am hearing a lot of comments about 'not flying airbus' from passengers. Lose one more airbus and the entire company could be out of business as its fly-by-wire and composite construction aircraft are grounded.
How much would that cost the industry?
How much would streaming FOQA or DFDR data cost?
There are open connections on the Iridium network that could be used - you don't have to fund INMARSAT
So Airbus and the airlines would rather risk being grounded and go bankrupt than stream DFDR data. Is this a logical business approach?
It need not be continuous but could auto-start on particular events to be cancelled by the crew if there is no crash. So turbulence above a certain value, any failures or exceptions would trigger a minimun of say 300 seconds streaming DFDR if not cancelled it would continue.
In this case if this auto-streaming had taken place it might already be apparent why the A330 crashed and retrofit action could be being taken on airframes perhaps with particular hardware or software versions. But no - we saved a few hundred dollars per flight and are happy to accept the risk of another A330 accident leading to a total grounding of all similar aircraft.
Is this a logical risk analysis?
Hmmmmm, the problem with that logic is the streaming data is unnecessary unless you lost another one. As long as the plane makes it back OK, you've got your data in the flight recorders. And by your own argument, if we do lose another one it would be too late for Airbus.
If Airbus is really hurting that bad, they better get one of their airplanes and start flying it around in bad weather. Use test pilots, not paying passengers.
I don't understand that comment about losing another one. At all. Not trying to hammer on ya, but that defies any logic I can muster. Once again, what would it *actually* cost to implement?
Here's another take: Airbus, Boeing et al. make certain things a requirement with the aircraft. Like requiring streaming data. Don't want to comply, "No airplane for you!" ;-) Simplistic, I know, but that changes the landscape a bit. This isn't a weight or space issue, how many modern *independent-of-aircraft-power* quad core physically hardened rack mounts can you fit in a very small box, or boxes? Lots.
If large scale data management is an issue, call the kids @ Google, they have some experience in that area. PR is a non-issue, seen any ads explaining the TSA taxes on the ticket I just bought for Deb? I haven't. Closest I've seen is Southwest making a point that what you see is what ya get, fare-wise, and that's about baggage. Do *you* look at the taxes on your tickets?
Bottom line for me, what's the problem utilizing proven, relatively inexpensive current technology to make all flights safer? And if it breaks in the first few revs, so what, we're exactly where we are right now, with a mysterious accident that most likely won't be solved.
Let me take it from the top. I find it strange that no one seems to be agreeing with me, so either someone slipped drugs into my chocolate so that I'm only making sense to myself, or somehow we're on parallel but different tracks.
I assume the proposal that's on the table is to take the data stream that's currently going to the black boxes and stream a copy of the data to safety. Now, unless I've misunderstood the idea, this is only to eliminate or substantially reduce the need to hunt for the black boxes. There's nothing about analyzing the data for anomalies that might have previously escaped notice or didn't arise to the level of a incident. Nor is there any plan to add a "back seat driver" to give advice in real-time. Those are interesting ideas, but I don't think that's what's been proposed.
So, if I've understood the idea correctly, this would only be an advantage if the airplane ended up in a smoking hole or a watery grave. If a/c makes it back to the gate, the effort to retrieve the boxes is trivial.
Now, there's two views on this: Long term and short term.
Long term, yes, it's a good idea. It may well save time doing an expensive search and might save data that would otherwise be lost. (One question that has been asked and so far not answered - how many times have we not been able to find the boxes or they had critical parts that were unreadable?) Still, it won't completely eliminate expensive searches. The black boxes are a great tool, but they are of limited help in cases of mechanical or structural failure. In some cases, we had to find the failed part to know what happened. The 747 that lost it's cargo door outside of HNL and the DC9 that lost all hydraulics due to the #2 engine are two that come to mind.
And yes, it would be a great help if AF 447 was so equipped. But it wasn't. We have to figure out where to go from here and not wish that something had turned out differently.
Short term, the public is having a crisis of faith in Airbus. The this idea is not going to help the immediate fear. Because in order for this idea to pay off, we have to loose another a/c. Yes, it will help prevent ones -after- that (which by then might be too late for Airbus), but it does nothing to protect the next one. (If not, what am I missing?) That's not going to go over with the public too well. To solve the short-term problem Airbus would be much better off flying some research missions into weather that pilots normally avoid.
As for cost, some one tell me what the bandwidth of the data is, what is the maximum number of running airplanes at any one time, and what the bandwidth of the Internet system is and then we'll talk. Without those numbers, I see a issue of scalability. Just because someone was able to send large attachments while in flight doesn't mean the system can support all the airplanes all the time. Even if it could, it's not going to be free. Someone is going to have to pay for that bandwidth used. Because bandwidth used can't be sold to someone else and more satellites cost big money.
And last, but not least, - money is what makes companies run. To implement this is all expense and no income. While the idea has potential benefits for the industry as a whole, I don't see *any* financial advantage to the company that steps forward first. Madison Avenue can try to make it a competitive advantage, but I think that's going to be a tough sell. Right now with everyone in survival mode, I don't see anyone doing this out of the goodness of their hearts or to add goodwill to their brand.
I haven't seen anyone in this thread suggest that bypassing a few smoking holes/deep oceans is the only purpose of streaming data.
Also, no need to fixate on F447 as a lost opportunity because this issue is not about what 447 didn't have, it's about what the next crashed airliner will or won't have. Losing an airliner at deep sea happens to put a fine point on the discussion, but this is not about one rare crash scenario.
Yes, it's going to cost money to stream data. It costs money to put an airliner in the air. Lots more money to crash one. Bandwidth is cheap and getting cheaper.
447 did transmit some useful data -- possibly more than we've heard about on the news, but it still looks like we're going to go deep-sea fishing for flight data and cockpit communication from a heavily computerized modern aircraft that was already capable of sending generic failure messages out to the living. Something wrong with that picture.
[The money] only comes out of someone else's budget if an accident only happens once. Imagine the effect on Airbus and the airlines flying them if there is another loss of an Airbus in convective weather in the next months and no cause had yet been found.
Its a risk analysis issue - Airbus has created a fleet based on replicated computer systems, fly-by-wire and composites. If one or more of these areas is _believed_ to be flawed then the entire Airbus series from the A319 to the A380 could be impacted. Similarly if your airline is based on one particular type or series your entire airline could be grounded.
Is that a risk worth taking? That is a commercial decision.
In the past streaming data over datalink was difficult and expensive now its easy and cheap and can use existing certified components. So the risk/cost of amelioration equation has changed.
From the other viewpoint suppose that the problem is caused by a low probability set of conditions that the software designers did not expect that causes the computers to fail-UNsafe _every_ time that set of conditions occurs. It would be really nice to know about that before multiple major disasters. It would certainly help the public perception of the industry.
I think we need a bit of perspective here. How many transport accidents have we had where the recorders were not recovered? No reason to spend a lot of money rushing in new technology to fix a non-existent problem.
As SESAR and NextGen move into implementation one of their requirements is high bandwidth reliable datalink. One of the standards being proposed in SESAR is WIMAX and IPv6. In simple terms WIMAX is like a far more powerful WiFi and a near earth orbit satellite system could provide more than 10mbs to a large number of users. (More than there are currently aircraft flying transoceanic). This bandwidth would allow streaming of DFDR and possibly even CVR from aircraft.
This is a business decision of course. But since the mid-80's we have had Air India 182 (bomb), TWA 800 (center fuel tank??), Swiss Air 111 (electrical fire), Egypt Air 990 (pilot initiated?) and now Air France 447 and that is just the Atlantic. Unfortunately, crashes of commercial wide-bodies into the ocean are NOT rare events and in each case there is an extended search for the DFDRs.
There is no technical reason why online streaming of DFDR should not be done.
It is a business risk analysis driven decision. But Airbus Industrie and Air France executives might be able to sleep easier if they had a better idea of why the AF447 A330 was lost.
Here's some actual money stuff: As of 2008 an Airbus 330-200 costs anywhere from 176.3 to 185.5 million US dollars ([url=http://www.airbus.com/store/mm_repository/pdf/att00011726/media_object_file_ListPrices2008.pdf]Airbus.pdf[/url]).
Insurance *may* cover what AF 447 was insured for, and some other issues, but doesn't pay for loss of revenue while the aircraft is replaced. And it sure ain't covering the cost of a brand new one. [url=http://www.kenyoninternational.com/in_the_news/08JUL%20-%20Regional%20International.pdf]This[/url] may be of interest. That's the trivial stuff, money-wise, and a problem for Air France and their customers. And their shareholders.
The cost of the investigation, which AF needs to be involved with aside from the authorities investigation may be large, but nothing near what the settlements with family members will be. The cost in reputation to Airbus is immeasurable, as is the trickle down effect of passengers that are most likely, as I type, checking what aircraft they're on for an upcoming flight. Now it's not an Air France problem anymore, it's every airline that flies the Airbus...and I doubt most will be checking model numbers.
An interesting (2005) comment from Airbus as regards monitoring and predictive maintenance is [url=http://www.atwonline.com/channels/maintenance/article.html?articleID=1139]here[/url], one part I thought of interest was this: "[i]Airbus soon will offer AIRMAN Onboard, which will allow cockpit crews to view the same analysis that occurs on the ground. An enhanced version that will permit the manufacturer to monitor all A380 flights from its headquarters in Toulouse will be standard equipment on that aircraft, according to Beams.[/i]" Not about streaming per se, but an indicator on how they've been thinking.
As regards bandwidth and number of aircraft aloft at a given moment, I do believe the quantities of data that any individual aircraft would produce could be compressed to next to nothing. It's data, not video. Previously someone mentioned encrypting/streaming the CVR data too. Great idea, NTSB has the key, period, not the airlines, no deal like what's going on right now as regards CVR spot checking (Colgan) regardless of flight outcome.
Hmmm, one other thing about costs, the U.S. is 'lending' the French Navy some gear. OK, now we're paying directly too, as well as for the NTSB folks that'll be involved in this.
Btw, no drugs in your chocolate, just differing points of view. This emphasis about 'cost' in some posts in the thread doesn't seem based on what those arguments seem to be about, mainly that no business is going to do something that isn't required, if it's not in their own self-interest. Let's see what the costs of the search for the boxes, the investigation, the years of litigation and settlements, plus the intangible aspects as regards Airbus in general are. And of course the simple cost of replacing the aircraft. Then tell me that even *with* the loss of AF 447 it wouldn't have been in their interest (AB and AF)to get real-time up and running. It may in fact have caught the rumored speed isuue before it went critical, though of course that's pure speculation on my part. And as to adding 'new' technology, as I believe someone else referred to it as, gimme a break, nothing new at all here.
"John, I would be interested in your opinion or the other airline (current/former)pilots on a comment from a VP with ALPA concerning the continuous monitoring/transmission of cockpit voice and other information now stored in the black boxes in real time. He was adamitly against this."
I see no reason to try to do a FOQA with the CVR. It is smoke and mirrors.
First, who is going to listen to hours and hours of CVR tapes? And who is going to spend the money to develop a program to scan the tapes? And what are you looking for? Many can not really explain what the sterile cockpit is and what is a violation except for blatant disregard.
The Continental 3407.. lots jumped on the bandwagon about the tape and yes, it was not a pristine cockpit BUT there WAS challenge and response, checklist, briefings, discussion about the wx and ice and concerns.
It is sort of like the progression from CRM to TEM and now SMS. Too often it seems we want to create benchmarks for behavior and use that as a standard for measuring. Nice but the problem is not everyone is going to solve the problem using the same tools.
We had a LOFT where there was a cabin fire shortly after taking off. Winds were 90deg to the runway and wx was 200 or lower. Some crews returned, blew through 10,000ft still running 340kts, declared an emergency, ran what checklists they could and demanded to land opposite direction. Other crews ran checklists (one even asked for holding to complete checklists and briefings) and briefed and took almost twice as long to get the plane on the ground.
So, which did better? And for the crews that took twice as long and briefed, did checklists, did all the required steps? Up or down...
What would I like? I would like to see the ability to blast FDR data securely to a data bank to preclude having to go on a huge hunt for a box the size of a toaster. THAT would be a meaningful step forward in air safety.
They are going to have to find the boxes off 447. They have to... without the box, it is all conjecture and without the box, 228 people will be dead and without an explanation of what happened.
Monitor CVRs? Scoff scoff...
The NSA is *now* scanning all the telecommunications they intercept for key words. That is public information which means they actually have better capabilities. And they're doing it basically in real time - there may be a lag but if they weren't interpreting the data as fast as it was coming in they'd be hopelessly far behind. Which means the capability already exists for computers to scan the tapes for whatever management wants. If the data becomes available it *will* be interpreted.
Near as I can tell, the Generic Union Position on using CVR data is that, outside of an accident, what the company's crew is doing in the company's airplane with a load of the company's passengers in the back is none of the company's business.
Never quite understood that line of reasoning....
Not that I'm the first one on line to defend unions, but I do see a tiny bit of logic in that. Basically, the same logic that would apply to ordinary office workers not wanting their telephone calls monitored or a recording device in their office recording everything they say.
I do think they'll get plenty more support from the union and its members if the data were encrypted and only unencrypted when there's an accident/incident. And in addition, its use would be legally limited to accident/incident investigation.
I think that you're on the right track with that.
If we could be assured that the information would be used only to promote safety the resistance would be significantly less. The CVR recordings are only supposed to be used for accident investigation now but some managements have used them for other purposes. Managers making comments in grievance proceedings that they wouldn't have known without having listened to the CVR, etc.
Then there's still the problem of nobody wanting to have every comment they make at work fed straight to their boss's ear. Treat people like children and they're a lot more likely to act like children.
I took a look at the FOQA info I could find, interesting. A good idea, mired in the fuzziness of multiple interpretations I guess.
I do have a question, if you're willing...in the U.S. the NTSB is going to release the CVR transcripts and the other detailed technical aspects of the investigations they conduct. Is your comment about the law here related to that, or the release of the FOQA data? The former needs must be imo. The latter, if it's supposed to aid in prevention, should never be allowed in the legal arena. Kinda of what you wrote, can't see why anyone would want to participate in that case. Then again I'm guessing a case could be made that if there was a pattern...and on it goes, don't have a clue as to how that's solved.
Being a computer sorta guy, I'd like to think that predictive software can only get better, and the more data collected would help make that so, much sooner (the streaming deal).
All parties have to agree on the program and anyone can withdraw at any time. It has happened when data was accessed by others besides the 'gatekeeper'.
Also, before an event can be entered into the program it has to be reviewed. As you no doubt read, it does not cover intentional deviations without reason. Flying 350kts at 500ft will not wind up in FOQA with no sanctions.
The real benefit of the data is having someone who can read the data and find the trends before the events become accidents or incidents. For example, one FOQA group found on average the fleet was flying final faster than Vref +10 resulting in longer landings, more brake wear, etc. A memo was put out asking guys to work on it. Results followed. The great thing about FOQA is it allows you to focus and it shows you what is REALLY happening on the line.
But this data should not be available for discovery and in the Louisville (SDF) accident, the judge said ComAir had to turn over the data. Let's face it.. the average juror isn't going to understand the intent of FOQA and I come in, show you that the information shows ABC Airline KNEW their pilots were flying 'too fast' (above the recommended Vref +10) and speed was a contributing factor. And they didn't stop it. Joe Sixpack is going to look at those weeping families and 'send a message' that such shenanigans are NOT to be tolerated. BAM! big awards.
It's not a matter of collecting the data. And data collected is used to predict. The classic was the B/C LOC at CLT for runway 23. Data showed the designed approach contributed to unstablized approaches and that info was taken to the FAA which, in turn, put an ILS on 23. And data showed that arrivals at CHS and ILM were often handled in a way that contributed to unstabilized approaches. Pilots had complained but HARD data was the convincing argument.
I'm a great believer in FOQA... maybe even a (gasp) radical. I said once that I would be willing for the company to pull 3 random flights of mine and when I came to training, we could work on MY weak areas, not industry trends or fleet trends but where I was weak. Why do ILSes if the data shows I do them repeatedly and precisely? Answer.. because the training program calls for it.
But FOQA data should be shielded from discovery. We know people lie or cover up when they believe punishment is the consequence of error. We have seen programs where immunity was removed and IMMEDIATELY the number of reports went down.
I am not against lawyers or going after wrongs or cultural lapses. But without proper safeguards, FOQA will be eroded and a great safety tool will be compromised.
I should read more carefully. I thought your [i]It has happened when data was accessed by others besides the 'gatekeeper'.[/i] reference was to an unauthorized release of the FOQA data. No idea as to how you prevent the legal system from doing what you describe.
The data is 'sterilized' and 'swept' of any identifying information. The only ones who are able to unlock the ciphers and put flesh back on the report is the 'gatekeeper'.
The 'gatekeeper' can contact the pilots or individuals involved to find out what happened when a deviation occurs but that is infrequent. In one incident, the story was a senior management 'stumbled' onto the information inadvertently. ?? It was enough to halt the program for a while.
And on the other end, some pilots believe any consequence is some form of punishment. I think there were a few cases where the event was to be resolved with some training and the pilot group balked. And they then withdrew from the FOQA.
It can be VERY political if any party wants to use the program as a lever to achieve goals outside the target of safety. Having said all that, the data should be secure and one initial concern was how to dispose of the information without it becoming Nixon's missing minutes.
Data streaming is NOT real time monitoring. Although those against the former will try to lump it into the latter.
Stream the data, secure repository, 30 day (or pick a number) retention, only available to national government accident investigation bodies after an incident.
Sort of like ATC tapes.
I agree up to a point. Initially myself and I think others were referring to near real-time FDR monitoring via streaming. At least that's what I was talking about. How the data is monitored depends on how that's configured at the receiving end. Trivial example: When I've broadcast SnowCam or AntCam...Live there's a variable delay, up to ~10 seconds. Those watching are 'monitoring' in near real-time, once the initial stream is buffered, plus that delay. I don't believe the CVR data was ever mentioned as a practical real-time monitoring goal, other than getting it safely stored, with the FDR data. That FDR data *could* be analyzed, close to real-time, plus the delays as mentioned. Of course that requires software that has perhaps more up-to-date predictive 'intelligence', or maybe it's available right now, I have no idea.
The more I hear about the [i]'pitot tubes - the instruments that measure the speed'[/i](sic) in the media, the more I am confused.
Obviously the change to another pitot tube design was not issued by Airbus as a mandatory requirement, or the change would have been done immediately. But there have been some allusions in the media to the reason being that they were more affected by icing - which I would have thought _would_ make the change to a new design mandatory.
Has anyone here got any idea what the actual Airbus requirements were for changing out the old pitot design for (presumably) a new one and what the trigger was for doing so? There must be a public maintenance instruction of some sort.
The Aussies put out an AD on Airbus pitots in [b] 2002 [/b]
7:53 PM ET 8/19/09
PARIS (AFP)--French search teams have failed to locate the black boxes of Air France-KLM (AF.FR) flight that crashed in the Atlantic en route from Rio de Janeiro to Paris in June, the French air accident bureau said Thursday.
Search teams have now wrapped up a second operation to locate the flight recorders of the Airbus A330, which crashed off the Brazilian coast on June 1 killing 228 people, and will now try to find a new way to continue looking.
The first search phase ended on July 10, when the batteries powering the black box's locator signals were thought to have run out. Underwater vessels launched a second search at the end of July, sweeping the site with sonar.
"The search having failed to locate the wreck of the aircraft, the BEA will gather an international team of investigators and experts in the coming weeks to exploit the data gathered with a view to launching a third search phase, and to determine its modalities and means," the BEA agency said.
Full discussion here.
Colgan Flight 3407 Discussion (
The crew was cleared to descend to 11,000 feet, and shortly afterward noticed "significant ice buildup" on the windshield and the leading edge of the wings, Chealander said. The flight- data recorder indicated a system that helps to de-ice the plane had been activated shortly before those comments were made, he said "Landing Gear Activated."
The landing gear was activated one minute before the end of the recording, and 20 seconds later the wing flaps were lowered, Chealander said. Within seconds, "severe pitch and roll" movements were recorded, he said. The crew tried to raise the gear and the flaps just before the recording ended. http://tinyurl.com/bq7e6c
I am VERY SURPRISED that the NTSB is already discussing the CVR and the indications of what seem to be a tailplane stall with the config change.
I think the NTSB has at least one outstanding recommendation concerning ice problems with this type turbo prop. -from a prior accident some years ago (Roselawn?).
Of course it's way too soon to even make a "cause" statement.
However, it seems like the initial data shows the crew was indeed using whatever deicing stuff was installed.
I was part of an accident investigation team at a turbo prop accident in Minnesota some years ago. Killed all on board around Christmas time.
We all thought it was a potential ice situation -but after some investigation and the CVR, it turned out to be a pilot problem -too low on the non ILS approach. (Well, there were a lot of other factors but I'll not go into those).
Did they pull back on the yoke also? Don't know yet, but we will.
At any rate, it was an event from which there was insufficient time and altitude to recover.
Autopilot was being used until a/c departed. Shaker and pusher activated.
All the Hawker jets I have flown have tail de-ice as do all the Cessna jets. Airbus' also have tail de-ice.
The only civilian jets I have flown that do not have tail de-ice are Boeings and the CRJ.
I'm sure none of this probably applies to the loss of Cogan Air, but APs are dumb.
necessitating constant slight pitch and power increases. A pilot hand flying
will notice that rather early. An AP covers it up until some mechanical
limit is reached, which can be mighty late for real corrective action.
Full Discussion here.