Showing posts with label incident. Show all posts
Showing posts with label incident. Show all posts

Monday, September 17, 2007

July - August 2007 Aircraft Accidents

Hi Readers: Back from the hospital - a huge bit of vertigo and a spiking blood pressure caught me unawares. Now I'll finish what I started. Looks like July and August 2007 were two months of aircraft accidents and incidents indicating some very bad judgment and failure to follow the rules. The weather played a part, too. NTSB is still investigating.

There were 72 aircraft accidents and 5 incidents in August compared to 199 accidents and 3 incidents in July. The fatal accidents in August totaled 26, with 55 fatalities, compared to 39 fatal accidents, with 73 fatalities (not including the Brazilian airline fiasco, taking 186 lives) in July.

The record for August indicates an improvement until we look at the type and nature of the accidents. And, as we go along, we'll keep in mind the question, "could these accidents and incidents have been prevented?". Although it will take a detailed study and review to know why and how, the answer, of course, is a resounding yes.

The flying hours for each month, which at this point would still be estimated, would indicate a slight increase in the accident rate. The incidents and the fatal accidents, however, give us the insight that we need, since the incident is the beginning of an accident and the fatal accident has reached and passed its reality.

Without going into the details, both the July and August incidents indicated pilot error, local and ground control errors, as well as poor coordination in the taxi, takeoff, and landing operations. All of the operations occured in daylight and during VFR conditions.
The July and August accidents occured worldwide, with the majority being in the continental U.S., with Alaska accounting for 8 accidents in July and 11 accidents in August.

The fatal accidents, particularly in Alaska, are revealing of multiple errors:
Weather Involved: July 2007 - 9 , August 2007 - 4
Pilot Error (Loss of control, etc.): Jul - 13 ; Aug 9
Engine Failure: Jul - 1 ; Aug 2
Experimental / Amateur failures: Jul 1 ; Aug - 5
Unknown / Unreported: Jul - 10 ; Aug - 2
Inflight Fire: Jul 1 ; Aug - 0
Medical Flight: Jul - 1 ; Aug - 1
Suicide: Jul - 0 ; Aug - 1
Uncertificated Flight: Jul - 0; Aug - 1
Helicopter tail rotor failure: Jul - 1 ; Aug - 1
Helicopter collision: Jul - 1 ; Aug - 0

The collision of 2 TV Channel news helicopters in Phoenix, AZ while watching a police persuit on the ground, as unusual as it was, showed inattention in flight and poor coordination of operations (in fact there were a total of five helicopters in the air in the same operation).

There were two fatal Part 135 sightseeing tour accidents out of Ketchikan, Alaska, one in July and one in August, both DeHavilland DHC-2 aircraft. Both directly involving VFR operations in IFR conditions of rain, fog, low clouds, and strong downdrafts. The July accident resulted in 5 fatalities and 4 serious injuries, and the August accident in 5 fatalities.

We will hope for better results in September. Thanks for listening.

RS

Friday, August 24, 2007

Near - Miss Incident of Jets at LAX

Now that everybody has heard about the near-miss incident of Westjet B-737 and Northwest Airlines Airbus A320 in daylight at Los Angeles airport on 8-16-07, let's take a quick look and see what did happen and why. NTSB is investigating and the factual report will be forthcoming as usual.
A runway incursion or a near-miss? Some, including NTSB are calling it a runway incursion. However, so far the facts reported show that an incursion did not occur. It was definitely an incident, one that could have been disastrous for all. As a pilot I shudder to think what could have happened, and I'm sure the pilots involved have already relived the incident several times since. The passengers - how lucky they were that a collision did not occur. From the nose of the Westjet B-737 to the wingtip of the Northwest Airbus there was all of 37 ft.
So let's sort out the facts (or the reported facts) at this point. The Airbus was cleared for takeoff on Runway 24 L. The Westjet B-737 had just landed on Runway 24R and was positioned on Taxiway Y, wanting to cross Runway 24 L. Reportedly, he was cleared by Ground Control to cross Runway 24L. The Airbus has started takeoff and reached about 155 knots, probably ready to rotate. The B-737 managed to remain clear - we don't know exactly where on Taxiway Y - reportedly crossing the hold short line but not entering Runway 24, either moving or stopped.
The Westjet B-737 had arived from Calgary, Canada carrying 136 passengers and the Northwest Airlines Airbus was taking off with 150 passengers. At this point it appears that the PIC of the Airbus was properly cleared for takeoff by the Tower Controller. ( I do wonder if the PIC observed the the Westjet movements, which would have been ahead of him.)
The PIC of the Westjet would have to been cleared by the Tower Controller to cross Runway 24L - he or the Ist Officer switched to Ground Control without authorization from the Tower Controller during exit on Taxiway Y. The Ground Controller apparently assumed that the Tower Controller had instructed the Westjet to cross Runway24L.
It appears that almost all of the blame lies with the Westjet Captain and the Ground and Tower Controllers. In takeoff and landing operations there is no room for assumptions. The coordination betwen Controllers in the Tower appears lacking and the misunderstanding between the Ground Controller and the Westjet, particularly on the part of the Ground Controller, was primary to the incident. I wonder too, if the ground airport radar in the Tower was functioning for a reference.
In most respects, the misunderstandings shown in the incident remain inexcusable - but they do happen. In fact, they are happening quite frequently over the continental U.S. We'll see what the NTSB Investigators have to say. Thanks for listening. R.S.