Crash of a De Havilland DHC-6 Twin Otter 300 in Murandi

Date & Time: Sep 8, 2005 at 0815 LT
Operator:
Registration:
9Q-CBO
Flight Phase:
Survivors:
Yes
Schedule:
Goma – Beni
MSN:
735
YOM:
1980
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
18
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Two minutes after takeoff from Goma Airport, the crew reported engine problem and decided to make an emergency landing near Murandi, Nyiragongo territory. The aircraft came to rest in a banana plantation, lost its right wing and was damaged beyond repair. Three passengers were injured while 17 other occupants escaped unhurt.

Crash of a Boeing 737-230 in Medan: 149 killed

Date & Time: Sep 5, 2005 at 1015 LT
Type of aircraft:
Operator:
Registration:
PK-RIM
Flight Phase:
Survivors:
Yes
Site:
Schedule:
Medan - Jakarta
MSN:
22136
YOM:
1981
Flight number:
RI091
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
112
Pax fatalities:
Other fatalities:
Total fatalities:
149
Captain / Total flying hours:
7522
Captain / Total hours on type:
7302.00
Copilot / Total flying hours:
2353
Copilot / Total hours on type:
685
Aircraft flight hours:
51599
Aircraft flight cycles:
51335
Circumstances:
On 5 September 2005, at 03:15 UTC, Mandala Airlines registered PK-RIM, operating as flight number MDL 091, a Boeing 737-200 departing for Soekarno-Hatta Airport, Jakarta from Medan. The previous flight was from Jakarta and arrived at Medan uneventfully. The same crew have flight schedule on the same day and returned to Jakarta. The flight was a regular scheduled passenger flight and was attempted to take-off from Polonia Airport, Medan, North Sumatra to Jakarta and it was the second trip of the day for the crew. At 02.40 UTC information from dispatcher, those embarking passengers, cargo process and all flight documents were ready. At 02.52 UTC, Mandala/MDL 091 asked for push back and start up clearance bound for Jakarta from the Air Traffic Controller/ATC, after received the approval from the ATC they began starting the engines. At 02.56 UTC, the controller cleared MDL 091 taxi into position on runway 23 via Alpha. At 03.02 UTC, MDL 091 received clearance for take off with additional clearance from ATC to turn left heading 120º and maintain 1500 ft. The MDL 091 read back the clearance heading 120º and maintains 1000 ft. The ATC corrected the clearance one thousand five hundred feet. The MDL 091 reread back as 1500 ft. Some of the passengers and other witnesses stated that the aircraft has lifted its nose in an up attitude and take off roll was longer than that normally made by similar airplanes. Most of them stated that the aircraft nose began to lift-off about few meters from the end of the runway. The ATC tower controller recalled that after rotation the plane began to “roll” or veer to the left and to the right. Some witnesses on the ground recalled that the airplane left wing struck a building before it struck in the busy road, then heard two big explosions and saw the flames. Persons on board in MDL 091, 5 crew and 95 passengers were killed, 15 passengers seriously injured and 2 passengers (a mother and child) were reported survived without any injuries; and other 49 persons on ground were killed and 26 grounds were serious injured.
Probable cause:
The National Transportation Safety Committee determines that probable causes of this accident are:
• The aircraft took-off with improper take off configuration namely with retracted flaps and slats causing the aircraft failed to lift off.
• Improper checklist procedure execution had lead to failure to identify the flap in retract position.
• The aircraft’s take off warning horn was not heard on the CAM channel of the CVR. It is possible that the take-off configuration warning horn was not sounding.
Final Report:

Crash of a Boeing 737-244 in Pucallpa: 40 killed

Date & Time: Aug 23, 2005 at 1509 LT
Type of aircraft:
Operator:
Registration:
OB-1809-P
Survivors:
Yes
Schedule:
Lima - Pucallpa - Iquitos
MSN:
22580
YOM:
1981
Flight number:
TJ204
Country:
Crew on board:
7
Crew fatalities:
Pax on board:
91
Pax fatalities:
Other fatalities:
Total fatalities:
40
Captain / Total flying hours:
5867
Captain / Total hours on type:
3763.00
Copilot / Total flying hours:
4755
Copilot / Total hours on type:
1109
Aircraft flight hours:
49865
Aircraft flight cycles:
45262
Circumstances:
Following an uneventful flight from Lima, the aircraft was descending to Pucallpa-Capitán David Abensur Rengifo Airport runway 02, an intermediate stop on the flight from Lima to Iquitos. As the crew approached the destination, weather conditions deteriorated with heavy rain falls, CB's and turbulences. On final approach, the aircraft was unstable and descended below the glide until it crashed in a swampy and wooded area located 3,5 km short of runway. The aircraft was destroyed by impact forces and a post crash fire. 58 people were injured, some seriously, while 40 other occupants including five crew members were killed, among them 34 Peruvian, three American, one Australian, one Colombian and one Spanish.
Probable cause:
The Commission determines the likely cause of the accident as follows:
- The decision of the flight crew to continue the final approach and landing at the airport of Pucallpa in severe weather (storm).
- The decision of the flight crew to descend unstabilized and not act to stop the steep descent to the ground at a descent rate of above 1500 feet per minute; what triggered the GPWS (Ground Proximity Warning System).
- The decision of the flight crew not avoid the storm, not choosing to conduct a landing on the other runway or divert to the nearest airport until weather conditions improved.
- The decision of the flight crew to penetrate the storm, it having been detected on weather radar aircraft approximately 190 miles in advance.
- The loss of the horizontal and vertical visibility of the flight crew while penetrating the core of the storm (severe hailstorm). Severe hail causes obscuration of the front windows of the aircraft and therefore the total loss of situational awareness.
Final Report:

Crash of a Boeing 747-251B in Agana

Date & Time: Aug 19, 2005 at 1418 LT
Type of aircraft:
Operator:
Registration:
N627US
Survivors:
Yes
Schedule:
Tokyo - Agana
MSN:
21709
YOM:
1979
Flight number:
NW074
Country:
Region:
Crew on board:
16
Crew fatalities:
Pax on board:
324
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7850
Captain / Total hours on type:
7850.00
Copilot / Total flying hours:
9100
Copilot / Total hours on type:
8695
Aircraft flight hours:
95270
Circumstances:
During the initial approach, the red GEAR annunciator light above the gear lever illuminated, and the landing gear warning horn sounded after the gear handle was selected down and the flaps were selected to 25 degrees. During the go-around, the captain asked the second officer (SO), "what do you have for the gear lights?" The SO responded, "four here." When all gear are down and locked on the Boeing 747-200, the landing gear indication module located on the SO’s instrument panel has five green lights: one nose gear light above four main landing gear lights. The crew then read through the "Red Gear Light Remains On (After Gear Extension)" emergency/abnormal procedure from the cockpit operations manual to troubleshoot the problem. Although the checklist twice presented in boldface type that five lights must be present for the gear to be considered down and locked, the crew did not verbalize the phrase either time. The captain did not directly request a count, and the SO did not verbally confirm, the number of gear down annunciator lights that were illuminated; instead, the flight crew made only general comments regarding the gear, such as "all gear," "all green," or "got 'em all." Because the crew believed that all of the gear annunciator lights were illuminated, they considered all gear down and locked and decided not to recycle the landing gear or attempt to extend any of the gear via the alternate systems before attempting a second approach. During all communications with air traffic control, the flight crew did not specify the nature of the problem that they were troubleshooting. Although the checklist did not authorize a low flyby, if the flight crewmembers had verbalized that they had a gear warning, the controller most likely would have been able to notify the crew of the nose gear position before the point at which a go-around was no longer safe. Multiple gear cycles were conducted after the accident, and the nose gear extended each time with all nose gear door and downlock indications correctly displayed on the landing gear indication module. Post accident examination of the nose gear door actuator found that one of the two lock keys was installed 180 degrees backward. Although this improper configuration could prevent proper extension of the nose gear, the actuator had been installed on the accident airplane since 2001 after the actuator was overhauled by the operator. No anomalies were found with the landing gear indication module, the nose gear-operated door sequence valve, and the nose/body landing gear selector valve.
Probable cause:
The flight crews' failure to verify that the number of landing gear annunciations on the second officer’s panel was consistent with the number specified in the abnormal/emergency procedures checklist, which led to a landing with the nose gear retracted.
Final Report:

Crash of a Boeing 737-31S near Grammatiko: 121 killed

Date & Time: Aug 14, 2005 at 1203 LT
Type of aircraft:
Operator:
Registration:
5B-DBY
Flight Phase:
Survivors:
No
Site:
Schedule:
Larnaca – Athens – Prague
MSN:
29099
YOM:
1998
Flight number:
ZU522
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
115
Pax fatalities:
Other fatalities:
Total fatalities:
121
Captain / Total flying hours:
16900
Captain / Total hours on type:
5500.00
Copilot / Total flying hours:
7549
Copilot / Total hours on type:
3991
Aircraft flight hours:
17900
Aircraft flight cycles:
16085
Circumstances:
On 14 August 2005, a Boeing 737-300 aircraft, registration number 5B-DBY, operated by Helios Airways, departed Larnaca, Cyprus at 06:07 h for Prague, Czech Republic, via Athens, Hellas. The aircraft was cleared to climb to FL340 and to proceed direct to RDS VOR. As the aircraft climbed through 16 000 ft, the Captain contacted the company Operations Centre and reported a Take-off Configuration Warning and an Equipment Cooling system problem. Several communications between the Captain and the Operations Centre took place in the next eight minutes concerning the above problems and ended as the aircraft climbed through 28 900 ft. Thereafter, there was no response to radio calls to the aircraft. During the climb, at an aircraft altitude of 18 200 ft, the passenger oxygen masks deployed in the cabin. The aircraft leveled off at FL340 and continued on its programmed route. At 07:21 h, the aircraft flew over the KEA VOR, then over the Athens International Airport, and subsequently entered the KEA VOR holding pattern at 07:38 h. At 08:24 h, during the sixth holding pattern, the Boeing 737 was intercepted by two F-16 aircraft of the Hellenic Air Force. One of the F-16 pilots observed the aircraft at close range and reported at 08:32 h that the Captain’s seat was vacant, the First Officer’s seat was occupied by someone who
2 was slumped over the controls, the passenger oxygen masks were seen dangling and three motionless passengers were seen seated wearing oxygen masks in the cabin. No external damage or fire was noted and the aircraft was not responding to radio calls. At 08:49 h, he reported a person not wearing an oxygen mask entering the cockpit and occupying the Captain’s seat. The F-16 pilot tried to attract his attention without success. At 08:50 h, the left engine flamed out due to fuel depletion and the aircraft started descending. At 08:54 h, two MAYDAY messages were recorded on the CVR. At 09:00 h, the right engine also flamed out at an altitude of approximately 7 100 ft. The aircraft continued descending rapidly and impacted hilly terrain at 09:03 h in the vicinity of Grammatiko village, Hellas, approximately 33 km northwest of the Athens International Airport. The 115 passengers and 6 crew members on board were fatally injured. The aircraft
was destroyed.
Probable cause:
Direct Causes:
1. Non-recognition that the cabin pressurization mode selector was in the MAN (manual) position during the performance of the:
a) Preflight procedure;
b) Before Start checklist; and
c) After Takeoff checklist.
2. Non-identification of the warnings and the reasons for the activation of the warnings (cabin altitude warning horn, passenger oxygen masks deployment indication, Master Caution), and continuation of the climb.
3. Incapacitation of the flight crew due to hypoxia, resulting in continuation of the flight via the flight management computer and the autopilot, depletion of the fuel and engine flameout, and impact of the aircraft with the ground.
Latent causes
1. The Operator’s deficiencies in organization, quality management and safety culture, documented diachronically as findings in numerous audits.
2. The Regulatory Authority’s diachronic inadequate execution of its oversight responsibilities to ensure the safety of operations of the airlines under its supervision and its inadequate responses to findings of deficiencies documented in numerous audits.
3. Inadequate application of Crew Resource Management (CRM) principles by the flight crew.
4. Ineffectiveness and inadequacy of measures taken by the manufacturer in response to previous pressurization incidents in the particular type of aircraft, both with regard to modifications to aircraft systems as well as to guidance to the crews.
Contributing Factors to the Accident:
1. Omission of returning the pressurization mode selector to AUTO after unscheduled maintenance on the aircraft.
2. Lack of specific procedures (on an international basis) for cabin crew procedures to address the situation of loss of pressurization, passenger oxygen masks deployment, and continuation of the aircraft ascent (climb).
3. Ineffectiveness of international aviation authorities to enforce implementation of corrective action plans after relevant audits.
Final Report:

Crash of a HESA IrAn 140-100 in Arak

Date & Time: Aug 12, 2005 at 1840 LT
Type of aircraft:
Operator:
Registration:
EP-SFD
Survivors:
Yes
Schedule:
Tehran – Khorramabad
MSN:
90-01
YOM:
2003
Location:
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
19
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
En route from Tehran to Khorramabad, while in cruising altitude, the right engine failed. The crew was cleared by ATC to divert to Arak Airport. After landing, the aircraft went out of control, veered off runway and came to rest. All 27 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Failure of the right engine for unknown reasons.

Crash of an Airbus A340-313X in Toronto

Date & Time: Aug 2, 2005 at 1602 LT
Type of aircraft:
Operator:
Registration:
F-GLZQ
Survivors:
Yes
Schedule:
Paris - Toronto
MSN:
289
YOM:
1999
Flight number:
AF358
Country:
Crew on board:
12
Crew fatalities:
Pax on board:
297
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
15411
Captain / Total hours on type:
1788.00
Copilot / Total flying hours:
4834
Copilot / Total hours on type:
2502
Aircraft flight hours:
28426
Aircraft flight cycles:
3711
Circumstances:
The Air France Airbus A340-313 aircraft (registration F-GLZQ, serial number 0289) departed Paris, France, at 1153 Coordinated Universal Time (UTC) as Air France Flight 358 on a scheduled flight to Toronto, Ontario, with 297 passengers and 12 crew members on board. Before departure, the flight crew members obtained their arrival weather forecast, which included the possibility of thunderstorms. While approaching Toronto, the flight crew members were advised of weather-related delays. On final approach, they were advised that the crew of an aircraft landing ahead of them had reported poor braking action, and Air France Flight 358’s aircraft weather radar was displaying heavy precipitation encroaching on the runway from the northwest. At about 200 feet above the runway threshold, while on the instrument landing system approach to Runway 24L with autopilot and autothrust disconnected, the aircraft deviated above the glideslope and the groundspeed began to increase. The aircraft crossed the runway threshold about 40 feet above the glideslope. During the flare, the aircraft travelled through an area of heavy rain, and visual contact with the runway environment was significantly reduced. There were numerous lightning strikes occurring, particularly at the far end of the runway. The aircraft touched down about 3800 feet down the runway, reverse thrust was selected about 12.8 seconds after landing, and full reverse was selected 16.4 seconds after touchdown. The aircraft was not able to stop on the 9000-foot runway and departed the far end at a ground speed of about 80 knots. The aircraft stopped in a ravine at 2002 UTC (1602 eastern daylight time) and caught fire. All passengers and crew members were able to evacuate the aircraft before the fire reached the escape routes. A total of 2 crew members and 10 passengers were seriously injured during the crash and the ensuing
evacuation.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The crew conducted an approach and landing in the midst of a severe and rapidly changing thunderstorm. There were no procedures within Air France related to distance required from thunderstorms during approaches and landing, nor were these required by regulations.
2. After the autopilot and autothrust systems were disengaged, the pilot flying (PF) increased the thrust in reaction to a decrease in the airspeed and a perception that the aircraft was sinking. The power increase contributed to an increase in aircraft energy and the aircraft deviated above the glide path.
3. At about 300 feet above ground level (agl), the surface wind began to shift from a headwind component to a 10-knot tailwind component, increasing the aircraft’s groundspeed and effectively changing the flight path. The aircraft crossed the runway threshold about 40 feet above the normal threshold crossing height.
4. Approaching the threshold, the aircraft entered an intense downpour, and the forward visibility became severely reduced.
5. When the aircraft was near the threshold, the crew members became committed to the landing and believed their go-around option no longer existed.
6. The touchdown was long because the aircraft floated due to its excess speed over the threshold and because the intense rain and lightning made visual contact with the runway very difficult.
7. The aircraft touched down about 3800 feet from the threshold of Runway 24L, which left about 5100 feet of runway available to stop. The aircraft overran the end of Runway 24L at about 80 knots and was destroyed by fire when it entered the ravine.
8. Selection of the thrust reversers was delayed as was the subsequent application of full reverse thrust.
9. The pilot not flying (PNF) did not make the standard callouts concerning the spoilers and thrust reversers during the landing roll. This further contributed to the delay in the PF selecting the thrust reversers.
10. Because the runway was contaminated by water, the strength of the crosswind at touchdown exceeded the landing limits of the aircraft.
11. There were no landing distances indicated on the operational flight plan for a contaminated runway condition at the Toronto/Lester B. Pearson International Airport (CYYZ).
12. Despite aviation routine weather reports (METARs) calling for thunderstorms at CYYZ at the expected time of landing, the crew did not calculate the landing distance required for Runway 24L. Consequently, they were not aware of the margin of error available for the landing runway nor that it was eliminated once the tailwind was experienced.
13. Although the area up to 150 m beyond the end of Runway 24L was compliant with Aerodrome Standards and Recommended Practices (TP 312E), the topography of the terrain beyond this point, along the extended runway centreline, contributed to aircraft damage and to the injuries to crew and passengers.
14. The downpour diluted the firefighting foam agent and reduced its efficiency in dousing the fuel-fed fire, which eventually destroyed most of the aircraft.
Findings as to Risk :
1. In the absence of clear guidelines with respect to the conduct of approaches into convective weather, there is a greater likelihood that crews will continue to conduct approaches into such conditions, increasing the risk of an approach and landing accident.
2. A policy where only the captain can make the decision to conduct a missed approach can increase the likelihood that an unsafe condition will not be recognized early and, therefore, increase the time it might otherwise take to initiate a missed approach.
3. Although it could not be determined whether the use of the rain repellent system would have improved the forward visibility in the downpour, the crew did not have adequate information about the capabilities and operation of the rain repellent system and did not consider using it.
4. The information available to flight crews on initial approach in convective weather does not optimally assist them in developing a clear idea of the weather that may be encountered later in the approach.
5. During approaches in convective weather, crews may falsely rely on air traffic control (ATC) to provide them with suggestions and directions as to whether to land or not.
6. Some pilots have the impression that ATC will close the airport if weather conditions make landings unsafe; ATC has no such mandate.
7. Wind information from ground-based measuring systems (anemometers) is critical to the safe landing of aircraft. Redundancy of the system should prevent a single-point failure from causing a total loss of relevant wind information.
8. The emergency power for both the public address (PA) and EVAC alert systems are located in the avionics bay. A less vulnerable system and/or location would reduce the risk of these systems failing during a survivable crash.
9. Brace commands were not given by the cabin crew during this unexpected emergency condition. Although it could not be determined if some of the passengers were injured as a result, research shows that the risk of injury is reduced if passengers brace properly.
10. Safety information cards given to passengers travelling in the flight decks of Air France Airbus A340-313 aircraft do not include illustrations depicting emergency exit windows, descent ropes or the evacuation panel in the flight deck doors.
11. There are no clear visual cues to indicate that some dual-lane slides actually have two lanes. As a result, these slides were used mostly as single-lane slides. This likely slowed the evacuation, but this fact was not seen as a contributing factor to the injuries suffered by the passengers.
12. Although all passengers managed to evacuate, the evacuation was impeded because nearly 50 per cent of the passengers retrieved carry-on baggage.
Other Findings:
1. There is no indication that the captain’s medical condition or fatigue played a role in this occurrence.
2. The crew did not request long aerodrome forecast (TAF) information while en route. This did not affect the outcome of this occurrence because the CYYZ forecast did not change appreciably from information the flight crew members received before departure, and they received updated METARs for CYYZ and Niagara Falls International Airport (KIAG).
3. The possibility of a diversion required the flight crew to check the weather for various potential alternates and to complete fuel calculations. Although these activities consumed considerable time and energy, there is no indication that they were unusual for this type of operation or that they overtaxed the flight crew.
4. The decision to continue with the approach was consistent with normal industry practice, in that the crew could continue with the intent to land while maintaining the option to discontinue the approach if they assessed that the conditions were becoming unsafe.
5. There is no indication that more sophisticated ATC weather radar information, had it been available and communicated to the crew, would have altered their decision to continue to land.
6. It could not be determined why door L2 opened before the aircraft came to a stop.
7. There is no indication that the aircraft was struck by lightning.
8. There is no information to indicate that the aircraft encountered windshear during its approach and landing.
9. The flight crew seats are certified to a lower standard than the cabin seats, which may have been a factor in the injuries incurred by the captain.
Final Report:

Crash of a Yakovlev Yak-40 in Caticlan

Date & Time: Jul 19, 2005 at 0958 LT
Type of aircraft:
Operator:
Registration:
RP-C2803
Survivors:
Yes
Schedule:
Manila - Caticlan
MSN:
9 43 05 37
YOM:
1975
Flight number:
ISL210
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
20
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Caticlan-Malay Airport, the three engine aircraft was too low and struck the ground short of runway 06. A tyre burst as it struck the raised lip of the runway. When removing the airplane from the runway the undercarriage collapsed. The aircraft came to rest after a course of few dozen metres. All 23 occupants escaped uninjured and the aircraft was damaged beyond repair. Caticlan Airport has a concrete runway of 950 metres long.
Probable cause:

Crash of an Antonov AN-24B near Malabo: 60 killed

Date & Time: Jul 16, 2005 at 1000 LT
Type of aircraft:
Operator:
Registration:
3C-VQR
Flight Phase:
Survivors:
No
Site:
Schedule:
Malabo – Bata
MSN:
7 99 011 04
YOM:
1967
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
54
Pax fatalities:
Other fatalities:
Total fatalities:
60
Circumstances:
After takeoff from Malabo Airport, the airplane encountered difficulties to gain sufficient height. It continued in a flat attitude until it impacted a hillside located about 19 km east of the airport, near Baney. The aircraft was totally destroyed and all 60 occupants were killed, among them several students flying to the continent for holidays.
Probable cause:
It was reported that the manifest showed a total of 35 passengers instead of 54. The aircraft, bought by Aerolineas de Guinea Ecuatorial in February 2002, was supposed to have its 1,000-hours maintenance check around January 2004, but due to financial problems, the company was unable to comply. The aircraft was sold to Equatair without the appropriate maintenance program completed in due time.

Crash of a Douglas DC-10-30ER in Chittagong

Date & Time: Jul 1, 2005 at 0853 LT
Type of aircraft:
Operator:
Registration:
S2-ADN
Survivors:
Yes
Schedule:
Dubai - Chittagong - Dhaka
MSN:
46542
YOM:
1979
Flight number:
BG048
Country:
Region:
Crew on board:
15
Crew fatalities:
Pax on board:
201
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Dubai on a flight to Dhaka with an intermediate stop in Chittagong, carrying 201 passengers and a crew of 15. Weather conditions at Chittagong Airport were poor with a visibility of 1,800 metres in rain, 5-7 oktas cloud at 700 feet, 3-4 oktas cloud at 1,300 feet, 0-2 oktas cloud at 2,600 feet, overcast at 8,000 feet with CB's, temporary visibility of 2 km and wind from 180 at 6 knots. On final approach, the aircraft was unstable but the captain decided to continue the descent. After touchdown on runway 23, the aircraft deviated from the centerline to the right, causing the right main gear to veer off runway. While contacting soft ground, it was torn off, causing the engine n°3 to be partially sheared off. The aircraft slid for few dozen metres before coming to rest in a grassy area along the runway. All 216 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
Wrong approach configuration on part of the crew who failed to follow the SOP's and his failure to initiate a go-around while the aircraft was unstable on short final.