The AI-generated cat pictures thread
6/13/2006 - SCOTT AIR FORCE BASE, Ill (AFPN) -- The results of an investigation into the C-5 Galaxy crash at Dover Air Force Base, Del., on April 3 found that human error was the cause, Air Mobility Command officials released today.
The accident investigation board determined the pilots and flight engineers did not properly configure, maneuver and power the aircraft during approach and landing.
Following a normal takeoff and initial climb, the C-5 aircrew observed a No. 2 engine “Thrust Reverser Not Locked” indication light. They shut down the No. 2 engine as a precaution and returned to Dover AFB. The board determined that during the return to the base:
-- The pilots and flight engineers continued to use the shut-down No. 2 engine’s throttle while leaving the fully-operational No. 3 engine in idle.
-- Both instructor and primary flight engineers failed to brief, and pilots failed to consider and use, a proper flap setting.
-- The pilots’ attempt at a visual approach to runway 32 resulted in the aircraft descending well below a normal glidepath for an instrument-aided approach or the normal visual flight rules pattern altitude.
-- The aircraft commander failed to give a complete approach briefing that would have included non-standard factors, configuration, landing distance and missed approach intentions.
All 17 people on board the C-5 survived the crash, but three crewmembers were seriously injured when the aircraft stalled, hit a utility pole and crashed into a field about a mile short of the runway. The other passengers and crewmembers sustained minor injures and were treated and released from local hospitals.
The aircraft was assigned to the 436th Airlift Wing and was flown by members of the 512th Airlift Wing, a Reserve associate unit at Dover. It was bound for Ramstein Air Base, Germany, and was carrying 105,000 pounds of replenishment supplies for the U.S. Central Command area of responsibility.
ALMOST MADE IT!
So they were flying, realized there was something wrong with engine #2 and shut it down. Then when lining up for their final approach they tried using it forgetting that the engine was shut off? I mean, couldnt they retract the flaps, and full throttle out of there and reattempt the landing? Seems like they were all just kind of pissing around and had no idea what was going on. I am by no means an expert flyer or claim to know anything about flying. My flying is when I get in a plane and go somewhere, a ride in a B17, and jumping out of a few planes skydiving.
Boost Pope
iTrader: (8)
Join Date: Sep 2005
Location: Chicago. (The less-murder part.)
Posts: 33,020
Total Cats: 6,588
This is a well-known phenomenon. Experts in human factors in aviation describe the concept of CRM, or Cockpit Resource Management. The basic premise is simple: design the system (both the hardware and the procedures) in such a way that the aircrew tend to remain alert and cognizant of the overall situation in which they are in. Flight is 99.9% about rote and routine, and when faced with an abnormal situation, it's easy to get distracted by focusing on the details of whatever seemingly important thing is happening at any given instant, and loose sight of the "big picture", such as the large, earth-shaped thing rapidly approaching outside the window.
That's what makes this situation in Tampa so incomprehensible to me. There is no indication that there was any emergency or abnormal situation whatsoever- nothing at all to explain how the crew completely lost track of where they were, and executed a perfect, controlled landing at a runway which in no way resembled their intended destination.
(Well, that's not 100% true. By coincidence, the runway at MacDill is 04/22, just like the long runway at TPF. But still, I can't imagine that it's that hard to tell them apart.)
Were you cutting aluminum with it? Years ago, I watched a guy explode a chop saw blade like that and leave a dude shaped pattern of pie shaped chop saw blade chunks in the steel locker behind him. We found out later that some jackass had been cutting aluminum unistrut with the saw, which imbeds itself in friction-type cutting blades and expands enough when you cut steel with it again to crack them. Which tends to propagate VERY rapidly at 10k+ rpm.
Were you cutting aluminum with it? Years ago, I watched a guy explode a chop saw blade like that and leave a dude shaped pattern of pie shaped chop saw blade chunks in the steel locker behind him. We found out later that some jackass had been cutting aluminum unistrut with the saw, which imbeds itself in friction-type cutting blades and expands enough when you cut steel with it again to crack them. Which tends to propagate VERY rapidly at 10k+ rpm.
Elite Member
iTrader: (1)
Join Date: Feb 2008
Location: Birmingham Alabama
Posts: 7,930
Total Cats: 45
I don't miss my construction job, where I used to have to use a chop saw quite often to cut concrete. How I never got injured by exploding discs is a mystery. I probably had 20+ of them come apart on me. I always tried to stand off to the side of the saw, which always made for excruciating back pain by the end of the day.