itemscope="itemscope" itemtype="http://schema.org/WebSite"> Airlaw, Author at Airlaw :: The Wolk Law Firm - Page 11 of 13

About Airlaw

For more than 50 years, The Wolk Law Firm has concentrated its practice in the area of aviation law, with Arthur personally generating verdicts and settlements of more than a billion dollars during the last decade alone. He is known for obtaining and on appeal, holding, the largest verdicts for each type of air accident claim in recent aviation history.

    The captain, the first officer, and the Department of Homeland Security

    Recently, two events captured the news media’s attention. One was a Delta Airlines Boeing 767 that landed on the taxiway instead of the runway at the Hartsfield Jackson International Airport. The other was a Northwest Airlines Airbus A320 whose crew failed to communicate with air traffic control or the company dispatch for more than an hour and a half, and missed its destination by 150 miles until the flight attendant knocked on the cockpit door to ask why there was no descent for landing.

    The first incident occurred when the Delta crew flew a lengthy international trip. When the Boeing 767 arrived at the airport, the runway end identifier lights were out of service (they’re the little white flashing lights that tell pilots where the runway starts) and the localizer was also shut down (the electronic pathway that guides pilots to the runway end). So, with an air traffic controller obviously asleep at the switch, the big B-767 landed on the taxiway right next to the runway. Under different circumstances, like another airplane on the taxiway, this could have been a disaster. You might ask how that could happen, but here are all the things that add up to this event.

    With all of the runways at the Hartsfield, giving landing clearance to an airliner on a runway with much of its safety equipment inoperative is inexcusable. The crew should have refused the landing clearance. But the FAA has for years contributed to the problem by using confusing lighting at the airport. I have argued with the guy in charge of airport signage for 30 years but since the idea wasn’t invented in his head, nothing gets changed for the better. The runway lights are orange, both sides and the centerline. The taxiway lights are green down the centerline and blue on each side. Since the centerline of some taxiway’s are green, and some are yellow like the runway and yes some are green and yellow at the end where the runway intersects, it’s no wonder that a pilot looking at them from afar can mistake a taxiway, especially a large one, for a runway. So the flight deck crew, tired after a long flight, looks at the myriad of lights and thinks the taxiway is to the left instead of the right because there is nothing to identify it clearly and lands on the taxiway. Nothing really unsafe here as long as the taxiway is unoccupied because the taxiways at the Hartsfield are as wide as runways at other airports. If the taxiway had totally blue lights it would have been unmistakable but, no, the FAA has a better idea, keep it confusing so one disaster or near disaster after another can happen. The controller too must have been glassy eyed because he didn’t warn the Delta flight and at that hour he had nothing else to do.

    All accidents and incidents have more than one cause. In this case it was the combination of no warning, no runway identifier lights, no localizer, confusing taxiway lighting, tired crew.

    The Northwest flight is another near disaster. The flight departed San Diego, CA for Minneapolis. Shortly after passing Denver, air traffic controllers were unable to raise the flight by radio. Company dispatch likewise couldn’t get the flight deck crew’s attention. The aircraft flew 600 miles, passed Minneapolis and then only after a flight attendant pounded on the cockpit door, the crew turned the airplane around and landed. The cockpit voice recorder was recorded over so the cockpit conversation that preceded the turnaround was unavailable. The flight deck crew first reported they were having a heated discussion and just lost situational awareness. Then they said they were working on their laptops, a prohibited flight deck activity. The FAA’s punishment was swift and not unexpected, emergency revocation of the flight deck crew’s pilots’ licenses, a vocational death knell to this very experienced and otherwise incident free crew. It is painful to see this unfold because the crew was obviously sleeping. Had they come clean right away and blamed it on scheduling, or interruption in their circadian rhythm from sleep deprivation, perhaps a little mercy would have been shown them at least on appeal.

    But never touched by the press was the fact that the Department of Homeland Security was more sound asleep than the crew. That aircraft was airborne far longer than any flight on 9/11 yet no fighters were scrambled to check on it, no steps were taken to protect cities, sensitive military or civilian installations from an aircraft that, for all the Department knew, was hijacked. Falling asleep and endangering the passengers by possibly running out of fuel is one thing but risking them being shot down is quite another. In short, everyone on that aircraft could have been dead either from a crash or a worst nightmare, being shot down for no good reason.

    What we need to ask ourselves is how did the Department of Homeland Security fail us again? It demonstrates to me that we have learned nothing from 9/11 and worse, after hundreds of billions spent, we are no better off eight years later.

    Now Congress, if it can interrupt its current investigation of the two concussions suffered annually in NFL play, should instead focus on why Homeland Security failed us and whether a Bugs Bunny alarm clock is needed in aircraft cockpits. More realistic however, should be the introduction of real time video of the cockpit crew steaming back to the dispatcher. This would obviate the need for a cockpit voice recorder and be a useful tool to address a growing problem of cockpit fatigue due to the boredom of automated aircraft. It would also vastly simplify accident investigation.

    This week was prophetic and lucky. The fatigue suffered from having nothing to do is risky, the absence of hundreds of deaths because of it is really lucky, and the incompetence of the Department of Homeland Security may sadly portend bad things to come.

    – Arthur Alan Wolk

    0

    Nine people dead and everyone is wondering how this could happen. The nut cases are out in force, shrieking that small aircraft are a menace and should be banned from New York airspace. The NTSB sent a go-team along with representatives of each of the aircraft makers and their engine builders to investigate the mid-air crash. If it had happened to anyone else, they would have sent a new hire with two weeks training.

    This cause of the accident is simple and anyone who has ever flown into New York’s airspace could have predicted something like it would happen. Even though Visual Flight Rules (VFR) aircraft regularly use this airspace, if a careful pilot wants to get radar flight-following he might as well try calling the President because no one answers.

    Altman didn’t have the chance to call Newark Approach Control before his aircraft was struck by the climbing helicopter

    At the same time, a Liberty Helicopters tour was about to embark on a sight-seeing flight from the 30th Street Heliport and enter the same densely populated airspace, flying Southbound over the Hudson while climbing.

    The helicopter pilot was climbing South in a blue helicopter that blended perfectly with the Hudson below while Steve, flying the Saratoga, was headed South.

    As the aircraft converged, the helicopter gaining altitude and the fixed wing no longer in a position to see the helicopter climbing, they either collided or the downwash from the helicopter literally sucked the air out from under the airplane’s right wing. The right wing of the aircraft contacted one of the rotor blades and was immediately sliced off. The helicopter rotor, now hopelessly unbalanced, tore off, shaft and all, and the two doomed aircraft fell to the river below.

    Recently received video of the crash shows that the Altman Piper was struck from the left and below by the helicopter. The video clearly establishes that Altman had the right of way as aircraft to the right have the right of way. The helicopter just crossed right in front of the Piper and it appears that unsuccessful evasive action by Altman may have preceded the collision by an instant.

    Anyone who has ever flown a low wing Piper knows the visibility limitations forward and down. Why did this happen? The answer is simple. First New York must make its radar separation services readily available to VFR traffic because the concept of “see and avoid” just doesn’t work. Second, the question must be answered whether the helicopter company pilots communicate their intentions on any frequency to warn other aircraft to look for them before they climb up into the stream of traffic. There is a frequency 123.05 for this purpose that is published on the Aeronautical Charts but it is a very crowded and often garbled frequency rendering it useless for traffic avoidance. Last, the choice of blue for the color of Liberty’s helicopters makes no sense given the crowded environment in which they operate.

    Nine people dead for nothing but the FAA’s failure, once again, to do its job. The FAA failed to regulate the Helicopter tour operators so they would announce their intentions or be in contact with air traffic control. The FAA failed to assure clear procedures for aircraft entering the stream of VFR traffic South and Northbound in this narrow corridor. In short the FAA created a free for all and this time instead of the helicopters crashing into themselves, which the usually do, they took another airplane along.

    The media’s talking heads are frightening in their complete ignorance of both the problem and the solution. Sometimes it’s more frightening to hear them talk than it is to know the facts because they have exposure that is far greater than their uninformed views deserve. I have flown this route many, many times. It is safe when pilots fly in a straight path at a single altitude until they transit the area. It is unsafe when others climb into the flow of traffic unannounced and with no air traffic control whatsoever.

    Rules of flight must exist in this corridor. Aircraft and helicopters travelling North must hug the Manhattan shore at an altitude of 600 feet or below. Aircraft and helicopters travelling South should hug the New Jersey shore and be no lower than 700 feet and below 1100 feet. All aircraft transiting the area should be talking to someone who is an air traffic controller. All aircraft climbing or descending should be required to be in positive air traffic control.

    Hopefully changes for the better will come out of this. I doubt it will happen because the FAA never does anything when a few innocent people die, it waits until an airliner dies before public pressure forces it to make changes.

    This accident and the unspeakable misery it has caused nine families is unforgiveable.

    – Arthur Alan Wolk

    0

    More information than previously reported was transmitted in real time

    As additional details about the crash of Air France 447 are released, we now know that more information than was previously reported was being transmitted in real time including speed and altitude excursions, g-forces and all system read-outs, including computer faults.

    Prior to the crash, Airbus had issued a bulletin instructing all crews to be certain, by comparing to global positioning systems that their airspeeds were being properly read by the computers from the Pitot-static Tubes on the nose of the aircraft.

    The suggestion is that these tubes can ice up in severe weather in spite of being heated. Here’s the reality – the reason for the odd airspeed differences is that in situations of severe turbulence the airspeed variations can be large because the wind direction and velocity are rapidly changing as is the flight altitude of the aircraft. In short, severe wind shear causes rapid changes in wind direction and velocity.

    The bulletin makes sense but as the information trickles in, it begins to appear that severe turbulence and a breakup is more likely the culprit – a very bad ride indeed. The aircraft must be found in order to determine just what broke first – the tail, parts of the tail or the main wing box, the wing or parts of the wing. Only then will we know if the testing to ultimate load required for transport category airplanes is both realistic and stringent enough.

    This never should have happened.

    Lastly, there are serious limitations on weather radar on-board, as well as on those people who must interpret it. With all of the computing power on the A-330, much weather data was available to be downloaded, not only from the on-board radar but also from ground and space-based facilities as well because the computers can make a better decision on whether and how to proceed in the face of severe weather. We need to go there.

    – Arthur Alan Wolk

    0

    Air France Flight 447 is down. Sadly, it is expected that all 228 aboard are lost. The earmarks are all too familiar. Severe weather and a loss of radar contact usually mean in-flight break-up and rapid descent. This would, of course, explain the lack of a distress call and automatic reporting of electrical failure and significant turbulence by the onboard real time condition reporting system.

    The aircraft went down in an area called the Intertropical Convergence Zone. This is an area where the Northern and Southern hemisphere winds and weather collide to make a perfect condition for severe convective weather. That means severe thunderstorms frequently exceeding 50,000 feet with damaging turbulence, hail, intense rainfall and lightning. On the night of the crash, this area was especially hot with thousands of miles of severe weather making circumnavigation impractical.

    Therefore, the only way to get from Rio to Paris was to penetrate this band of severe weather, a daunting task for even the best aircrews flying the most sophisticated airliner. There is no coincidence that shortly after entering this area of severe weather the aircraft was lost. Whether it was due to an encounter with severe turbulence or a lightning strike that exploded a fuel tank can best be determined when the wreckage is found, and surely it will be one day.

    The cockpit voice and flight data recorders will also be very helpful but the automatically transmitted data already portends the turbulence, electrical anomalies and tragic end. This is why cockpit voice and flight data recorder information should be transmitted real time to home base.

    Coincidentally, an Airworthiness Directive had been issued in 2005 by the French authorities requiring float valve changes in the trim fuel tanks of this aircraft model’s horizontal stabilizers. The purpose was to avoid lightning or static electricity setting off an explosion in those tanks. The compliance time was quite lengthy and, while this aircraft was built in 2005, it is not clear whether it had the benefit of the improved floats. If it didn’t, or the fix was ineffective, a lightning strike on the trim tanks could have been a catastrophe that even the best crew would have been unable to avoid.

    It is, therefore, quite possible that the old problem of airliner exploding fuel tanks has reared its ugly head again. While better fuel tank standards have been published and bantered about the industry and governments since TWA 800 exploded in 1996, none of the legacy airplanes have benefited from the new standards and this Airworthiness Directive, which aimed to chip away at the problem.

    Aircraft radars have come a long way, providing flight crews with far better weather avoidance information than ever before. Unfortunately, weather avoidance is not weather penetration, but the demands of airline flying and schedules often blur the difference.

    Avoidance means not going there, penetration means getting into it and avoiding the damaging weather by skillful use of the radar. The letter works most of the time but not always. Aircraft and human graveyards are full of the results of severe weather penetrations because there are limits on even the best radars. Intense rainfall absorbs signal strength and confuses returns, intense cells hide others just behind and give a false sense of security that safety is just a few miles away, when the worst may be yet to come.

    Last year a computer failure pitched an identical aircraft so violently, the crew thought there was a clear air turbulence encounter. The manufacturer said it was impossible and could not have occurred. Later it appeared that indeed the impossible could happen. One out of many computers could cause a dangerous and sudden pitch excursion that might have led to structural failure. That must be ruled out in this case. While turbulence may have been the initiator, computer failure may have increased its lethality.

    No one wants an accident. No one deliberately tempts an accident with a planeload of families in the back and pilots who likewise want to get home alive up front. Indeed, they are the first to go. But whether this accident is the result of mechanical failure, the failure to simply remain on the ground in the face of impassable weather or the unlikely act of a saboteur, it is nonetheless the worst of nightmares come true.

    Weather. Mechnical failure. Equipment malfunction. It looks like any one of these may have played a role. Whatever the ultimate cause, with today’s technology there is no reason for an airliner accident. With the prospect that this single field of human endeavor may one day be accident free, these deaths must not be in vain.

    – Arthur Alan Wolk

    0

    HAWKER 800 CRASH IN MINNESOTA
    Cockpit voice recorder transcript released

    The NTSB just released a transcript of the cockpit conversations of the captain and first officer of a crash that took their lives and six others in Minnesota last summer. There were no surprises here. The flight crew flew into an area of very severe weather with the airport literally surrounded by thunderstorms that reached as high as fifty thousand feet and had spawned at least one tornado. They experienced turbulence and heavy rain as they approached the airport, which had a wet runway from a recent very heavy shower.

    The crew violated the sterile cockpit rule – no non-pertinent conversation below ten thousand feet, distracted themselves by fooling with the radar tilt when they had the runway in sight, and failed to properly conduct both the approach checklist and the pre-landing checklist. Worse yet, they failed to extend full flaps, dooming their flight. Without full flaps deployed they could not activate the lift dump feature in the Hawker jet, an absolutely mandatory condition if they ever hoped to luck out and stop on a runway that was too short for this aircraft under those conditions.

    The lift dump system extends spoilers both above and below the wing. Without it, the airplane doesn’t place enough weight on the wheels early enough to spin them up and allow the anti-skid equipment to work. In fact, with the engines at idle thrust, an attempted go-around was futile given the normal time it takes for a crew to react and change the aircraft configuration.

    As in most aircraft accidents, there is more than one cause. Anxiety over the weather, the rough ride, the short runway, the non-pertinent conversation, and the failure to complete the checklist all combined to doom this flight. The failure to anticipate the heavy weather, the effect of water on the short runway, the inability of the aircraft to safely operate within the available runway contributed to poor decision-making by this crew. Sadly, even a crew that is well trained, skillful and has the best of intentions also becomes the victim of a combination of events that only they could avoid – a chain that must be broken if they and their passengers are to survive. It didn’t happen, and they too paid with their lives.

    Every pilot talks about the near accident he has had with the bravado that only a hero (in his own mind) can bring to the discussion. The problem is that if the stars line up and the events build in an inexorable combination of troubles, one day those pilots won’t be able to tell their story. No doubt these pilots were careful, decent, well-intentioned men. Unfortunately this disaster began with faulty pre-flight planning, faulty appreciation of the heavy weather that would be at the destination, faulty cockpit crew coordination that led to the careless skipping of what for this airplane was critical to a successful landing, full flaps.

    This accident will mean nothing if it doesn’t serve as a lesson to all pilots that the Federal Aviation Regulations, known as operating rules, are minimum standards. That means that even if they are complied with to the letter, they may not be enough to successfully complete a flight. The failure to meet those minimum requirements, however, is a virtual guarantee of an accident.

    Regardless of what position The Wolk Law Firm must take in the litigation for the deaths of the passengers that follows this accident, all of us, including the families of those passengers who have suffered unspeakable losses, lament the unnecessary deaths of everyone aboard.

    – Arthur Alan Wolk

    0

    CRIMINALIZATION OF AIR DISASTERS

    While such proceedings may satisfy the public’s zeal to punish those responsible, the result is that the flow of information necessary to correct aviation problems dries up over the long term because of the fear that such information will be used for criminal prosecution in the event of accidents.

    It is bad enough that manufacturers and airlines now hide what they do, or more importantly what they don’t do, in an effort to escape civil liability for accidents. Criminalization has always been fraught with the specter of witnesses using their Fifth Amendment rights not to incriminate themselves (which has the effect of impeding investigations that might result in safety improvements).

    Moreover, public authorities, whether prosecutors or public investigators, do a terrible job at investigating aircraft accidents and are too often the tools of manufacturers and airlines. Plaintiffs’ lawyers do the majority of aircraft accident investigations in the United States and spend far more, examine more intensively and extensively, and take sworn testimony more often to get to the bottom of these accidents. Criminalization will impede, not enhance, these efforts. What we need is more zealous sanctions when airlines and manufacturers hide information from the certifying authorities, distort warnings received from the field and flat out lie during civil proceedings. We need fewer judges who are selected for their promise to deter plaintiffs’ lawsuits; we should go back to hiring judges based on their demonstrated lack of bias and predilection.

    This issue has been around for years and is most often discussed in countries where civil litigation does not exist the way it does in the United States. Where there is no suitable vehicle to get to the truth civilly, criminalization is the fall-back position taken out of frustration. The real solution is to expand civil litigation systems in countries that don’t currently have them so that safety is enhanced rather than deterred by the regressive effects of criminalization.

    – Arthur Alan Wolk

    0

    At this stage of aviation history, there is no reason for this disaster and both the horror and pain it has caused to so many families

    One hundred fifty-three people were killed when a fully-loaded Spanair MD-82 crashed on takeoff from the Madrid airport on August 20, 2008. Witnesses describe an explosion in the left engine and the aircraft falling to the runway, veering off and then exploding into an inferno.

    About one hour before the crash, the crew was reported to have aborted a takeoff because of a high temperature warning, known as an overtemp, from the left engine. Troubleshooting took place and the aircraft was again dispatched for a three-hour flight to the Canary Islands. The aircraft was full of fuel and the outside temperature was a warm 86 degrees Fahrenheit.

    It is inexplicable and horrendous that an aircraft such as this was cleared for service without an engine change when they couldn’t possibly have known what damage resulted from the overtemp. This situation in a jet engine is a serious matter requiring extensive investigation, not merely an hour’s worth of troubleshooting. It does not happen without good, and usually serious, cause including imminent failure of hot section components, failure of compressor and fan assemblies or likely turbine disintegration.

    Jet engines nearly always telegraph their imminent failure and this one surely did. It was ignored. The Pratt and Whitney JT8D engine has had a long and satisfactory service history starting with the Boeing 727, 737, DC-9 and all the MD-80’s. While generally reliable, it has exploded all too frequently and is the subject of numerous service bulletins and airworthiness directives by the Federal Aviation Administration as well as aviation safety agencies in other countries. Some have exploded so violently that the containment rings that are designed to prevent penetration of debris into other critical aircraft components have proved to be insufficient.

    When the MD-82 was built and certified, it was supposed to be able to safely fly with one engine if the other failed after reaching V1 (the speed at which it becomes safe to continue the takeoff in spite of the failure of an engine). However, the claim was substantiated by test pilots who know the engine will be simulated to fail, and not by flight crews who are totally surprised by the event on a hot day while fully loaded.

    It is not surprising that the airplane didn’t fly because expecting humans to perform to perfection is unreasonable, and the temperature and weight were likely well beyond the test parameters. At the controls were Spanair test pilots who were also victims of a cascade of events that came together to create this tragedy.

    At this stage of aviation history, there is no reason for this disaster and both the horror and pain it has caused to so many families. Airline travel can and ought to be 100 percent safe if people do their jobs. This was an unnecessary accident.

    – Arthur Alan Wolk

    0

    A Hawker 800 executive jet aircraft crashed at a small airport in Minnesota, south of the Twin Cities on July 31, 2008. Witnesses describe a touchdown on a wet runway, a roll-out, then the application of power and a crash just beyond the end of the runway. All aboard were killed, either from impact or the ensuing fire.

    The crew had successfully diverted around heavy weather and was landing in an area of moderate rain showers. Just before the crash, a wind shear alert was given (a rapid change in wind direction and velocity). Normally, a flight crew will add as much as 10 knots to the landing reference speed in the event of wind shear. The aircraft made it to the airport and the runway, and presumably the lift dump system was deployed, which should have allowed the aircraft to stop in 4,000 feet on a dry runway, according to the flight manual. It is typical for jet aircraft to touch down in the first 1,000 feet but, due to the wind shear, the first 1,500 feet may have been used. Therefore, except for the wet runway, 5,500 feet should have been sufficient for landing to a full stop, leaving about 750 to 1,000 feet remaining, if all went as expected. However, because of reported tail winds and standing water on the runway, it was questionable whether stopping in the available distance was possible. Hydroplaning, further increasing stopping distance, was also likely.

    For all, or some of these reasons, the landing didn’t go as expected. The crew elected to “go-around,” meaning they would have had to stow the left dump spoilers and flaps, and trim and apply takeoff power. The engines, likely idle by this time, would have had to spool up and the aircraft would have needed to accelerate again to take-off speed. The time to make the decision to go-around, stow the lift dump and achieve take-off thrust could have taken 10 to 15 seconds and used up another 1,000 to 1,500 feet of runway. That left precious little, or no, runway for the aircraft to accelerate to lift-off speed.

    The aircraft did not leave the ground. Wheel tracks show that it left the pavement, traveled in the runway safety area–still on the ground–struck an antenna array, and then fell into a culvert where it burned. While there is no doubt the crew tried to save the aircraft, the decision to go-around on that size runway may have doomed the flight.

    Investigators will review the cockpit voice recorder and, if equipped, the flight data recorder for clues and will look at the wreckage to determine the aircraft configuration at time of impact.

    This information should confirm that unless there was a mechanical malfunction, this accident was preventable, like so many others of a similar type.

    • First, a go-around from idle thrust and with lift dump deployed on a 5,500 foot runway with this aircraft is nearly impossible under normal circumstances.
    • Secondly, aircraft performance charts are prepared to sell airplanes and bear little resemblance to actual performance achieved by average pilots in the field.
    • Thirdly, a pilot must always plan for contingencies and on this approach there was wind shear, lightning in the distance in all quadrants, heavy weather nearby and a short wet runway.

    Even the best flight crew can find itself without options under circumstances like these. The tragedy of this accident reminds us all that aviation safety means no accident, whether it’s a mechanical malfunction, the combination of foul weather and a short runway, a faulty decision to go-around based upon inadequate aircraft performance information or just a mistake.

    No conclusions can or should be drawn about this accident as the investigation has just begun, but these are some thoughts that bear consideration regardless of the ultimate findings.

    -Arthur Alan Wolk

    0

    NASA DEEP SIXES IMPORTANT AVIATION SAFETY INFORMATION
    By Arthur Alan Wolk

    NASA ordered the contractor to destroy “embarrassing” information

    (October 22, 2007) NASA spent $8,500,000 of our money to study aviation safety the right way: interview pilots in strict confidence so they would feel free to disclose what they see as critical safety failures in our aviation transportation system without fear of retaliation.

    Now NASA, instead of releasing the information which shows that the FAA is totally inept at gathering safety information, has ordered the contractor to destroy it because it would be embarrassing to government and the airlines.

    This stonewalling of public information obtained in the ordinary course of its duties is unforgivable and a disgrace. The data shows that the FAA is totally in the dark about aviation safety and could benefit from this NASA data because it would demonstrate how and why the FAA doesn’t have a clue what’s going on in the National Airspace System.

    The reason no one talks to the FAA is obvious. The FAA will prosecute anyone from whom it receives information that relates to safety of flight even if the purpose of the disclosure is to improve safety. Moreover the FAA totally discounts information from the field about safety defects in aircraft so mechanics and pilots are loathe to report troubling problems as no action is ever taken. In addition, the FAA rats out the whistleblowers and gives them no protection, hanging them out to dry, to lose their jobs and to go it alone. Therefore, they have absolutely no incentive whatsoever to help the FAA.

    NASA, on the other hand, gives a “get out of jail free card” with the report of sensitive safety information so there is an incentive to provide timely and helpful information that can be useful in preventing accidents. What is troubling about this revelation, however, is that a serious effort was made by NASA due to a perceived aviation safety need to get up close and personal so it could acquire the most useful data and now it will “deep six” it because it would embarrass another agency of government – the FAA – that agency being solely responsible for the safety of flight!

    In short, instead of using this information as a tool to improve the FAA, the most ineffective agency of government, NASA sees fit to destroy the information instead. Hide critical information that might be embarrassing to the government? Never!

    – Arthur Alan Wolk

    0

    Composite Structures For Aircraft Not All They Are “Cracked Up” To Be
    Recent NTSB safety recommendation concerning

    A recent NTSB Safety Recommendation should be of great concern to aircraft manufacturers, airlines and their passengers. It concerns the “disbonding” of the composite rudders on some A300 Airbus airliners. It seems hydraulic fluid delaminates the bonding agent and allows the plies of composite material to separate. The danger is that strength of the composite structure is compromised, such that it is no longer useful as an aircraft structure and can result in a catastrophic separation in flight.

    Everyone loves composites these days. Why? Because they are light, rigid, strong and increasingly easy to build. They are stronger than their steel and aluminum counterparts and are infinitely lighter. Aircraft manufacturers, ever mindful of the needs of their airline customers, especially fuel costs, are trying to make structures lighter so less power and less fuel will carry the same number of passengers less expensively. Also, since large composite panels can now be made efficiently, small aluminum panels can be substituted with huge sheets of composite structure, cutting manufacturing costs and the price of the finished aircraft.

    The rush to larger and more complex structures, however, must be tempered with the very high risk of in flight break-up and a deadly crash caused by unforeseen structural failure or disbonding from the ever present leakage of hydraulic fluid from the myriad of hydraulically operated systems in aircraft, like landing gear, flaps and flight controls. These systems, operating at thousands of pounds per square inch pressure, leak frequently, and a leak where fluid accumulates and remains for long periods can be deadly.

    What’s needed is a substitute for the highly toxic, corrosive and composite destroying hydraulic fluid now in use, one that will not disbond composite structures. If this step is not taken at once, we are asking for trouble — and it will be big trouble. New aircraft are increasingly large, carrying more and more people. An Airbus 380 carrying 800 people cannot shed a major structure with impunity. Already the wing failed a critical ultimate load test, and the less than optimal results were double talked away by engineers. No amount of double talk will adequately explain to hundreds of families the industry’s failure in the face of this knowledge to make absolutely certain that hydraulic fluid doesn’t cause an airplane to crash.

    Hopefully, and I am not optimistic, the pressures of competition will cause aircraft manufacturers in both hemispheres to address this deadly problem. They have been forewarned!

    -Arthur Alan Wolk

    0