Crash of a Beechcraft 60 Duke in Wilmington: 1 killed

Date & Time: Dec 4, 2007 at 0722 LT
Type of aircraft:
Operator:
Registration:
N105PP
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Wilmington – Allentown
MSN:
P-105
YOM:
1969
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1080
Circumstances:
According to a witness, prior to arriving in the run-up area the pilot lowered the airplane's flaps. After the right flap fully extended, the flap key on the drive shaft inside the 90-degree drive assembly adapter fractured, in overload, in the direction of flap extension. Before takeoff, the pilot raised the flaps; however, with the fractured key, the right flap would have remained fully extended. The pilot could have identified this condition prior to takeoff, either visually or by means of the flap indicator, which received its input from the right flap actuator. The pilot subsequently took off, and the airplane turned left, but it is unknown at what point the pilot would have noted a control problem. The pilot climbed the airplane to 250 to 300 feet and allowed the airspeed to bleed off to where the airplane stalled and subsequently spun into the ground. Airplane manufacturer calculations revealed that the pilot should have been able to maintain control of the airplane at airspeeds over 70 knots. According to the pilot's operating handbook, the best two-engine angle of climb airspeed was 99 knots and the best two-engine rate of climb airspeed was 120 knots.
Probable cause:
The pilot's failure to maintain adequate airspeed during a split flap takeoff, which resulted in an aerodynamic stall. Contributing to the accident were the failure of the right flap drive mechanism and the pilot's failure to verify that both flaps were retracted prior to takeoff.
Final Report:

Crash of a Piper PA-61P Aerostar (Ted Smith 601P) in Waterford: 2 killed

Date & Time: Apr 27, 1997 at 2052 LT
Registration:
N885JC
Flight Type:
Survivors:
No
Schedule:
Allentown – Leesburg
MSN:
61-0826-8163434
YOM:
1981
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1600
Captain / Total hours on type:
525.00
Circumstances:
During arrival at night, the flight was being controlled by a developmental controller (DC), who was being supervised by an instructor (IC). The pilot (plt) was instructed to descend & cross the STILL Intersection (Int) at 3,000 ft. STILL Int was aligned with the localizer (loc) approach (apch) course, 10.1 mi from the apch end of runway 17 (rwy 17); the final apch fix (FAF) was 3.9 mi from the rwy. About 5 mi before reaching STILL Int, while on course & level at 3,000 ft, the plt was cleared for a Loc Rwy 17 Apch. Radar data showed the aircraft (acft) continued to STILL Int, then it turned onto the loc course toward the FAF. Shortly after departing STILL Int, while inbound on the loc course, the acft began a descent. Before the acft reached the FAF, the DC issued a frequency change to go to UNICOM. During this transmission, the IC noticed a low altitude alert on the radar display, then issued a verbal low altitude alert, saying, 'check altitude, you should be at 1,500 ft (should have said '1,800 ft' as that was the minimum crossing altitude at the FAF), altitude's indicating 1,200, low altitude alert.' There was no response from the plt. This occurred about 2 mi before the FAF. Minimum descent altitude (MDA) for the apch was 720 ft. The acft struck tree tops at 750 ft, about 1/2 mi before the FAF. The IC's remark 'you should be at 1,500 ft' was based on an expired apch plate with a lower FAF minimum crossing altitude; the current minimum crossing altitude at the FAF was 1,800 ft. Apch control management had not made the current plate available to the controllers. Investigation could not determine whether a current apch plate would have prompted an earlier warning by the controllers.
Probable cause:
Failure of the pilot to follow the published instrument (IFR) approach procedure, by failing to maintain the minimum altitude for that segment of the approach.
Final Report:

Crash of a Gulfstream GII in New York

Date & Time: Mar 25, 1997 at 0510 LT
Type of aircraft:
Operator:
Registration:
N117FJ
Survivors:
Yes
Schedule:
Allentown - New York
MSN:
229
YOM:
1978
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9900
Captain / Total hours on type:
3860.00
Copilot / Total flying hours:
21000
Copilot / Total hours on type:
4000
Aircraft flight hours:
6743
Circumstances:
All positions at LaGuardia Tower were combined to the local control position from 0011 EST until after the accident. At about 0430 EST, ground personnel in 'Vehicle 1277' (communicating on ground control frequency), were cleared on runway 13/31 to perform 'lighting maintenance.' Later, during repair of centerline lights and while N117FJ was inbound to the airport, Vehicle 1277 stalled on runway 13/31. Personnel of Vehicle 1277 attempted to restart the vehicle, but were unable, so they shut off all vehicle lights to reduce electrical load, and again attempted to restart the vehicle, but to no avail. At 0507 (during darkness), N117FJ made initial call to the tower for landing. The controller acknowledged the call, scanned runway 13/31, did not see Vehicle 1277, and cleared N117FJ to land on runway 31. At 0510, personnel of Vehicle 1277 observed N117FJ in the approach/landing phase and radioed ground controller that they were stuck on the runway. The controller then radioed, 'go-around, aircraft on the runway go-around, aircraft on the runway go-around, seven fox juliet go-around.' Moments later, N117FJ impacted Vehicle 1277. The FAA ATC Handbook stated, 'Ensure that the runway to be used is clear of all known ground vehicles, equipment, and personnel before a departing aircraft starts takeoff or a landing aircraft crosses the runway threshold.'
Probable cause:
The tower controller's inadequate service by clearing the airplane to land on the same runway, where he had previously cleared a maintenance vehicle to perform maintenance to the runway centerline lights. Factors related to the accident were: darkness, partial failure of the runway centerline lights, the electric maintenance vehicle's loss of engine power, and a failure to have adequate emergency backup lighting.
Final Report:

Crash of a Mitsubishi MU-2B-60 Marquise in Allentown

Date & Time: Jan 19, 1996 at 1930 LT
Type of aircraft:
Registration:
N888TP
Survivors:
Yes
Schedule:
Wilkes Barre - Allentown
MSN:
1541
YOM:
1982
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2265
Captain / Total hours on type:
350.00
Aircraft flight hours:
2788
Circumstances:
The flight was on the ILS approach to runway 6, broke out of the clouds at 500 feet, and then re-entered the clouds. The airplane had not yet touched down when it drifted to right of the runway centerline and struck a snow bank located in the grass to the right of the runway, between the runway and the taxiway. The pilot stated he was just starting the missed approach when the accident occurred, and '...that there was no indication of a malfunction of the aircraft.' The reported ceiling was, 100 sky obscured, and the visibility was 1/4 mile, wind 040 degrees, 6 knots.
Probable cause:
The pilot's failure to comply with IFR procedures in that he attempted an instrument approach with visibility below the required minimums, and his delayed execution of a missed approach. A factor was the reduced visibility due to clouds.
Final Report:

Crash of a Beechcraft B65 Queen Air near Madison: 2 killed

Date & Time: May 16, 1992 at 1400 LT
Type of aircraft:
Registration:
N30RR
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Allentown - Charlottesville
MSN:
LC-186
YOM:
1965
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
6003
Circumstances:
The instrument rated pilot was en route to his granddaughter's graduation exercises scheduled for the following day. He had received two preflight weather briefings from flight service and he was advised that marginal VFR conditions existed en route, and instrument meteorological conditions at his destination, and that VFRflight was not recommended. A witness who was below the mountain said he heard a low flying aircraft overhead. He stated that he caught a glimpse of the airplane and said it was 'well below the crest of the mountain' heading south. The weather as reported by the witness was about 200 overcast and visibility below 1 mile in fog. He also mentioned that the clouds had obscured the mountain. Shortly thereafter, he heard what was later determined to be the collision. Search personnel located the burning wreckage on top of Mitchells mountain 50 miles north of Charlottesville. Both occupants were killed.
Probable cause:
The pilot initiated VFR flight into known adverse weather conditions. Contributing to the accident was low ceiling, high terrain, and low altitude.
Final Report:

Crash of a Learjet 35A in Morristown: 1 killed

Date & Time: Jul 26, 1988 at 0740 LT
Type of aircraft:
Operator:
Registration:
N442NE
Flight Type:
Survivors:
Yes
Schedule:
Allentown - Morristown
MSN:
35-442
YOM:
1981
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4810
Captain / Total hours on type:
2100.00
Aircraft flight hours:
4274
Circumstances:
The crew was positioning the aircraft in preparation for a revenue flight and executing a non-directional beacon (NDB) approach to runway 05. The captain reported that the copilot was flying the aircraft. However, the captain stated that he took control of the aircraft during the approach and made some control corrections before returning control of the aircraft to the copilot. Radar data indicated that aircraft control was erratic throughout the approach and that the airspeed and descent rates were high (3,000 fpm sink rate) shortly before the accident. The aircraft struck a fence short of the runway and impacted the ground. The captain said he realized the aircraft was drifting left of course but did not correct it. He said he told the copilot to add power twice during the approach. The copilot's training history indicated difficulty in control, scan of instruments, and with instrument procedures. Company management described the captain as passive and the copilot as aggressive. Supervision of training and operations by management and surveillance of the company by the FAA was considered inadequate by NTSB.
Probable cause:
Occurrence #1: loss of control - in flight
Phase of operation: approach - faf/outer marker to threshold (ifr)
Findings
1. (c) flight controls - improper use of - copilot/second pilot
2. Overconfidence in personal ability - copilot/second pilot
3. (f) inadequate recurrent training - copilot/second pilot
4. (f) inadequate surveillance of operation - faa (organization)
5. (f) airspeed - improper - copilot/second pilot
6. (f) proper descent rate - exceeded - copilot/second pilot
7. (c) supervision - inadequate - pilot in command
8. (f) interpersonal relations - pilot in command
9. Insufficient standards/requirements,airman - company/operator mgmt
----------
Occurrence #2: in flight collision with terrain/water
Phase of operation: approach - faf/outer marker to threshold (ifr)
Final Report:

Crash of a Beechcraft B200 Super King Air in Jasper

Date & Time: Jun 23, 1987 at 0619 LT
Registration:
N859DD
Survivors:
Yes
Schedule:
Birmingham - Jasper - Allentown
MSN:
BB-859
YOM:
1981
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11000
Captain / Total hours on type:
2000.00
Aircraft flight hours:
2966
Circumstances:
The pilot obtained a weather briefing for his proposed flight from Birmingham, AL to Jasper, AL to Allentown, PA. He did not file a flight plan for the 35 mile flight from Birmingham to Jasper, however, he did file a flight plan for the proposed flight from Jasper to Allentown. He stated that he 'felt like he got a little slow and the tail stalled' during his VFR landing approach at Jasper. The aircraft contacted the ground at the east end of the east-west runway on a northerly track. The aircraft continued on the northerly track for 288 feet before colliding with trees. The aircraft was destroyed by the post crash fire. Witnesses reported fog in the area and the pilot reported that he had encountered patches of fog on the flight from Birmingham.
Probable cause:
Occurrence #1: in flight collision with terrain/water
Phase of operation: approach
Findings
1. (f) weather condition - fog
2. (f) light condition - dawn
3. (c) proper alignment - not attained - pilot in command
4. (c) airspeed - not maintained - pilot in command
5. (c) stall - inadvertent - pilot in command
6. (f) go-around - not performed - pilot in command
----------
Occurrence #2: in flight collision with object
Phase of operation: approach
Findings
7. (f) object - tree(s)
Final Report:

Crash of a Cessna 402B in Meadville

Date & Time: Nov 1, 1982 at 0900 LT
Type of aircraft:
Operator:
Registration:
N402DL
Survivors:
Yes
Schedule:
Allentown - Meadville
MSN:
402B-0598
YOM:
1974
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5500
Captain / Total hours on type:
400.00
Aircraft flight hours:
2592
Circumstances:
The pilot approached high and fast for landing on runway 04. The wind was from 240° at 10 to 12 knots. The aircraft floated and after touchdown, the pilot was unable to stop on the wet, downsloping runway. After departing the runway, the aircraft continued down a steeper slope and into an area of brush and trees. All three gear collapsed, there was leading edge spar damage on both wings, and the right side fuselage skin, forward of the right wing, was damaged.
Probable cause:
Occurrence #1: overrun
Phase of operation: landing - roll
Findings
1. (f) weather condition - tailwind
2. (f) wrong runway - selected - pilot in command
3. (c) distance - misjudged - pilot in command
4. (c) airspeed - misjudged - pilot in command
5. (c) go-around - not performed - pilot in command
6. (f) airport facilities,runway/landing area condition - downhill
7. (f) airport facilities,runway/landing area condition - wet
8. (f) aircraft performance,hydroplaning condition - water
----------
Occurrence #2: complete gear collapsed
Phase of operation: landing - roll
Findings
9. (f) terrain condition - downhill
10. (f) terrain condition - high vegetation
11. Landing gear - overload
----------
Occurrence #3: on ground/water collision with object
Phase of operation: landing - roll
Findings
12. (f) object - tree(s)
Final Report:

Crash of a Beechcraft C-45H Expeditor in Slatington

Date & Time: Jun 29, 1979 at 0613 LT
Type of aircraft:
Operator:
Registration:
N281M
Flight Type:
Survivors:
Yes
Schedule:
Charleston - Allentown
MSN:
AF-644
YOM:
1954
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6042
Captain / Total hours on type:
2000.00
Circumstances:
On approach to Allentown-Bethlehem Easton Airport, the crew encountered limited visibility due to foggy conditions and low ceiling. The twin engine aircraft descended below the glide, struck trees and crashed in a wooded area located in Slatington, about 10,5 miles short of runway 13 threshold. The aircraft was destroyed and both occupants were injured.
Probable cause:
Collision with trees during initial approach due to improper IFR operation. The following contributing factors were reported:
- Low ceiling,
- Fog,
- Visibility two miles or less.
Final Report:

Crash of a Rockwell Shrike Commander 500S at Selfridge AFB

Date & Time: Mar 12, 1977 at 2015 LT
Registration:
N303E
Survivors:
Yes
Schedule:
Allentown - Selfridge
MSN:
500-3092
YOM:
1971
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2600
Captain / Total hours on type:
50.00
Circumstances:
On approach to Selfridge AFB, the pilot reported low fuel pressure when the left engine failed shortly later. In relative poor weather conditions with low ceiling, rain and fog, the airplane lost height then struck trees and crashed. The pilot, sole on board, was seriously injured.
Probable cause:
Engine failure on final approach for undetermined reasons. The following contributing factors were reported:
- Improper IFR operation,
- Low ceiling,
- Rain,
- Fog,
- Low fuel pressure reported by the pilot on approach.
Final Report: