New Mil-Web Program Tackles Fatigue-Related Aviation Accidents
Sun, 24 May '09
"FlyAwake" Produced By Air National Guard
A new Web-based program is helping military pilots and aircrews "FlyAwake," thanks to the combined efforts of the District of Columbia Air National Guard's 201st Airlift Squadron and the National Guard Bureau. "We were noticing the number of fatigue-related mishaps were quite high, and we needed to do something about it," said Air Force Capt. Lynn Lee. "So we took a look at what was out there, and the 201st Airlift Squadron's fatigue modeling program seemed to have the answer."
...
Research has shown that as fatigue goes up, cognitive effectiveness goes down, and the risk of an accident increases exponentially. "We want to stop that before it even gets to the pilots," she said. "So we're backing it up to the mission planning stage."
Air Force and Navy accident investigations have used fatigue modeling for some time to determine if fatigue was a factor, she noted. The new Web-based program gives squadron commanders and mission schedulers easy access and quick responses. In 2007, a safety idea from the 201st Airlift Squadron's commander, Air Force Col. Gary Akins, led to creation of a proactive fatigue modeling program to allow identification and mitigation of high-risk fatigue areas prior to mission departure. Walter Reed Army Research Institute had developed a set of algorithms, Lee said, which are extremely accurate in predicting fatigue, given an individual's sleep and work history.
To mitigate a projected fatigue risk, the 201st Airlift Squadron would add a crew member or shift take-off or landing times if possible, she added, and would design nap rotations to minimize fatigue at the critical events during the flight.
"The program was shown [to be] very successful at the 201st, ... [and] we used it for about six months," Lee said. "At that point, Lt. Col. Ed Vaughan, our previous Air National Guard chief of flight safety, spearheaded bringing it to the rest of the Guard."
In 2008, the Defense Safety Oversight Council funded joint-service implementation of the program, under the name "FlyAwake." Feedback on the test site from flight surgeons, physiologists, schedulers and pilots is being incorporated into the release next month of "FlyAwake 2.0." The new version also will include a new intelligent sleep model based on crew surveys, technical studies and other data, Lee said.
...
"Eventually, tools like this will become part of the safety culture of the flying community," she said. "The first step is to get buy-in at all levels and demonstrate the program's efficacy.
...
Agreed. Too much is being focused on the commute, and not enough on the ridiculous typical 14 hour days.
Scheduled duty time should not exceed 10 hours, period. We're not machines, and need to be focused and concentrated on what we are doing, in other words rested.
I know I get tired after 8 hours already, it's complete BS to be able to schedule a crew for up to 14 hours in 1 day, and for that to be standard operating procedure, with up to 16 hours being the legal FAA limit. That's only 8 hours from you being at work flying an airplane for 24 hours. Unbelievable.
And all of this on top of the ridiculous wages we earn for what we do.
"Standup/continuous duty/highspeed/illegal" overnights shall not be permitted.
I can see the following happen soon - all commuter are reauired to report to your base 12 to 24 prior designated report time.![]()
Behind the door is the magic term.
Also limiting the ability of flipping times around (such as starting a trip at 5 in the morning on day one and ending at midnight on the last day).
On the other hand, aside from shorter duty days, would any of these suggestions have really helped the CA and FO on 3407? They were both coming from days off. I know it's not the popular thing to say among commuters, but don't commuters bear the responsibility of showing up for work with adequate rest? If that meant the CA got a hotel room the night prior, and the FO commuted out the day prior to spend the night in EWR so be it. If rest is truly an issue, then you can't say "Give us shorter days, longer overnights, etc" yet not address the issue (which really corresponds to this accident) of showing up from hard commutes fatigued.
Behind the door is the magic term.
Also limiting the ability of flipping times around (such as starting a trip at 5 in the morning on day one and ending at midnight on the last day).
As the ALPA safety guy told the NTSB a week or so ago, there is no universally safe amount of rest; it depends upon the proposed flying, and the flying performed in the previous several days. 36 hrs might not even be sufficient after a super-long-haul flight, even with augmented crews.All rest periods will be 12 hours, regardless of duty length
Any duty that exceeds 12 hours (situations outside the operators control) will be followed by 36 hours of rest (keeps you on the same clock)
As the ALPA safety guy told the NTSB a week or so ago, there is no universally safe amount of rest; it depends upon the proposed flying, and the flying performed in the previous several days. 36 hrs might not even be sufficient after a super-long-haul flight, even with augmented crews.
I was talking with a friend who flies the B747 at UPS out of ANC. He commutes from SDF up there, and does trips pretty much exclusively to Asia. When discussing how the job was affecting his body, he told me it was "brutal." Without eating right, a lot of exercise, and time off to recuperate, it would kill him. Our lives down here in the lower 48 are not much different.