Crash of a Cessna 414A Chancellor in Atlantic City: 1 killed

Date & Time: May 17, 1986 at 2330 LT
Type of aircraft:
Registration:
N414NY
Flight Phase:
Survivors:
Yes
Schedule:
Atlantic City - Atlantic City
MSN:
414A-0242
YOM:
1979
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4010
Captain / Total hours on type:
76.00
Aircraft flight hours:
2054
Circumstances:
During takeoff ground run, at a speed of 95 knots, the pilot pulled the control wheel back to lift off. The control wheel, according to the pilot, would not go back more than about 2 inches; which is less than half the normal full aft travel. The aircraft reached a speed of about 105 knots and had traveled more than half of the runway length when the pilot aborted the takeoff. The pilot was unable to stop the aircraft on the runway. The aircraft went off the runway and subsequently collided with an occupied car that was on a nearby street. The investigation revealed the left side VOR indicator had loosened from its mounting clamp on the instrument panel and it was laying against the control wheel tube, behind the instrument panel, limiting the control wheel to 2.5 inches of rearward travel. The pilot stated that he removed the control lock before engine start and performed a flight control check before takeoff. All four occupants were injured while on person in the car hit by the aircraft was killed.
Probable cause:
Occurrence #1: on ground/water collision with object
Phase of operation: takeoff - roll/run
Findings
1. (f) flight/nav instruments, course indicator - disconnected
2. (f) flt control syst, elevator control - movement restricted
3. (c) aircraft preflight - inadequate - pilot in command
----------
Occurrence #2: overrun
Phase of operation: takeoff
Findings
4. (c) aborted takeoff - delayed - pilot in command
5. Terrain condition - runway
6. (c) distance - inadequate - pilot in command
7. Aircraft performance - exceeded
8. (c) all available runway - exceeded - pilot in command
9. (c) judgment - inaccurate - pilot in command
----------
Occurrence #3: on ground/water collision with object
Phase of operation: takeoff
Findings
10. Object - vehicle
Final Report:

Crash of a Dassault Falcon 50 in Teterboro: 3 killed

Date & Time: Nov 10, 1985 at 1722 LT
Type of aircraft:
Operator:
Registration:
N784B
Flight Type:
Survivors:
No
Site:
Schedule:
Morristown - Teterboro
MSN:
118
YOM:
1982
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
8265
Captain / Total hours on type:
817.00
Circumstances:
A Dassault Falcon 50 jet (N784B) and an Air Pegasus Piper PA-28-181 Archer (N1977H) collided about 1500 feet over the towns of Fairview and Cliffside Park, New Jersey, USA. The Falcon 50 was cleared for a standard instrument approach procedure in visual meteorological conditions and was in a left turn to position itself on the downwind leg to runway 19 at the Teterboro Airport, and the PA-28 was transiting the airport traffic area from west to east when they collided. The accident occurred 4 1/2 miles east-southeast at the edge of the airport traffic area in visual meteorological conditions. Both airplanes had been in radio contact with the Teterboro control tower. The flightcrew, the only occupants aboard the Falcon 50, and the pilot and two passengers onboard the PA-28 were killed. The Falcon 50 crashed into an apartment building killing one resident and seriously injuring two bystanders.
Probable cause:
A breakdown in air traffic control coordination which resulted in an air traffic conflict and the inability of the DA50 flightcrew to ‘see and avoid' the other aircraft due to:
- An erroneous and inadequate traffic advisory and
- The physiological limitations of human vision and reaction time at night.
Air traffic control management contributed to the accident by failing to insure that controllers were following prescribed procedures and by failing to recognize and correct operational deficiencies.
Final Report:

Crash of a Convair VT-29B in Trenton

Date & Time: Jun 19, 1985 at 0702 LT
Type of aircraft:
Operator:
Registration:
N155PA
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Trenton - Detroit
MSN:
322
YOM:
1953
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7000
Captain / Total hours on type:
2500.00
Aircraft flight hours:
16900
Circumstances:
The copilot begun takeoff with 2,700 rpm and 52 to 53.5' of manifold pressure (mp). Water injection was not used although 12 gallons was available. At 150 to 250 feet agl, the left engine lost power and the left propeller auto feathered. The captain took control and took action to verify left engine feathering. Neither pilot moved any of the other engine controls. A turn was initiated to return to the airport, but the aircraft began losing speed and altitude. Subsequently, it crash landed in a partly wooded area short of an open field and burned until firefighting personnel arrived. The impeller was demolished by fire, but evidence of debris from the impeller was found in the left engine intake and on top of its #3 and # 11 piston. The company's stated policy was to use water (wet takeoff), except when precluded by mechanical malfunction or lack of additional fluid; however, 4 dissimilar power charts were found in the aircraft. Takeoff weight was 38,670 lbs. Performance manual showed aircraft capable of 420 fpm climb with 12° of flaps, one prop feathered, landing gear up, dry power (no water). Max power setting was 2,700 rpm and 56' mp for dry takeoff; 2,800 rpm and 59.5' mp for wet takeoff. Both pilots were seriously injured.
Probable cause:
Occurrence #1: loss of engine power (partial) - mech failure/malf
Phase of operation: takeoff - initial climb
Findings
1. (c) eng assembly, blower/impeller/integral supercharger - failure, total
2. Propeller feathering - performed
----------
Occurrence #2: forced landing
Phase of operation: maneuvering - turn to landing area (emergency)
Findings
3. (c) throttle/power control - improper use of - pilot in command
4. (f) information unclear - company/operator management
----------
Occurrence #3: in flight collision with terrain/water
Phase of operation: maneuvering - turn to landing area (emergency)
Findings
5. (f) object - tree(s)
6. (f) terrain condition - rough/uneven
Final Report:

Crash of a Beechcraft A100 King Air in Cedarville: 2 killed

Date & Time: Feb 1, 1985 at 2147 LT
Type of aircraft:
Registration:
N72BS
Flight Type:
Survivors:
No
Schedule:
Ridgeland – Millville
MSN:
B-113
YOM:
1972
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
17300
Captain / Total hours on type:
4000.00
Circumstances:
The two atp rated pilots were en route back to their home base airport flying on an IFR flight plan in actual instrument weather conditions. Communications with ATC controllers was normal. During a night localizer approach into Millville municipal airport, an ATC specialist observed the aircraft passing through the localizer track and issued a vector for re-interception. The aircraft was subsequently observed tracking inbound on course. The pilot reported crossing the om. This was the last transmission heard from the pilot and was routine. The aircraft crashed into a wooded area just beyond the om and was destroyed in a post impact fire. Post accident examination of the wreckage revealed evidence to indicate the left engine was producing less power than the right engine at impact. Both occupants were killed.
Probable cause:
Occurrence #1: in flight collision with object
Phase of operation: descent - normal
Findings
1. (f) weather condition - low ceiling
2. (f) weather condition - fog
3. (f) weather condition - rain
4. (f) light condition - dark night
5. (c) ifr procedure - improper - pilot in command
6. (c) proper altitude - not maintained - pilot in command
----------
Occurrence #2: loss of engine power
Phase of operation: approach
Findings
7. Engine assembly - failure,partial
8. (c) engine assembly - undetermined
Final Report:

Crash of a Learjet 25 in Newark: 2 killed

Date & Time: Mar 30, 1983 at 0514 LT
Type of aircraft:
Registration:
N51CA
Flight Type:
Survivors:
No
Schedule:
Chicago - Newark
MSN:
25-030
YOM:
1969
Flight number:
CA27
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
5100
Captain / Total hours on type:
1600.00
Copilot / Total flying hours:
4112
Copilot / Total hours on type:
1488
Aircraft flight hours:
5750
Circumstances:
The aircraft was on a night check courier flight. During arrival, the indicated airspeed was well above the legal limit of 250 knots for flight below 10,000 feet. Runway 04R was selected for landing after the crew were advised that their original choice (runway 11) was noise sensitive. They were advised not to descend below 2,000 feet until on final approach. The turn to final was completed about one mile from the runway at an altitude of approximately 700 feet. A steep (5°) final approach was flown with an estimated 1,000 fpm rate of descent. On landing, the aircraft bounced, banked/turned to the right, then it hit the ground, right wing first and burned. An exam of the wreckage revealed the aircraft was configured with the gear extended, the flaps down 20° and the spoilers retracted. No evidence of a preimpact part failure or malfunction was found. The trim was set for a heavy right wing and the fuel switches were set to x-feed fuel. Toxicological checks showed that both pilots had used or been exposed to marijuana and had CO2 in their blood from smoking; use of medication (phenylpropanolamine) by copilot. Evidence of possible fatigue/stress to both. Both pilots were killed.
Probable cause:
The probable causes of this accident were:
- Loss of control following ground contact,
- An unstabilized approach,
- Impairment of the flightcrew judgment, decision making, and flying abilities by a combination of physiological and psychological factors.
Final Report:

Crash of a Rockwell Aero Commander 560E in Livingston: 2 killed

Date & Time: Nov 20, 1982 at 1614 LT
Operator:
Registration:
N3827C
Flight Type:
Survivors:
No
Schedule:
Blairstown - Teterboro
MSN:
560-0744
YOM:
1959
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
730
Circumstances:
Aero Commander 560E, N3827C (27C) was returning from Blairstown where it had been flown for minor maintenance. The pilot was on an IFR flight plan, cleared by New York tracon to proceed at 2,000 feet msl on a radar vector of 170° for an ILS approach to the Teterboro Airport. The aircraft was equipped with an altitude encoding transponder that was being used. The pilot was advised of numerous targets at his 12 o'clock position. At approximately the same time, Cessna 182Q, N96402 (402), was on a flight from the Kupper Airport to Ramapo Airport. A direct route between these airports would have intersected the nw edge of the New York TCA where positive control began between 1,800 and 7,000 feet msl. The pilot was proceeding VFR with no flight plan and was not in radio communication with any ATC facility. 402 was equipped with a transponder that was operating, but had no altitude encoding capability. As the aircraft converged, 402 was on a northeasterly heading. The planes collided about 1 mile inside the TCA. Then impacted the ground approximately 1,500 feet apart. A map was found in 402 with a line drawn between the airports and intersecting the TCA. All three occupants in both aircraft were killed.
Probable cause:
Occurrence #1: midair collision
Phase of operation: approach
Findings
1. (f) air/ground communications - not attained - pilot of other aircraft
2. (f) procedures/directives - not followed - pilot of other aircraft
3. (f) traffic advisory - not obtained - pilot of other aircraft
4. (f) unsafe/hazardous condition - not identified - ATC personnel (dep/apch)
5. (c) visual lookout - inadequate - pilot in command
6. (c) visual lookout - inadequate - pilot of other aircraft
Final Report:

Crash of a Beechcraft E18S in Lakewood

Date & Time: Aug 13, 1982 at 1800 LT
Type of aircraft:
Registration:
N380MA
Survivors:
Yes
Schedule:
Lakewood - Lakewood
MSN:
BA-237
YOM:
1957
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
25000
Captain / Total hours on type:
2000.00
Aircraft flight hours:
11300
Circumstances:
Prior to flight the spark plugs on both engines were replaced due to minor engine vibration and the landing gear retract system wiring repaired due to the gear not retracting electrically on a prior occasion. After takeoff the gear would not retract electrically and the passenger had to crank up the gear manually. After the parachute jump the pilot shut down the left engine to isolate the vibration. He then started the left engine and feathered the right engine. Unable to unfeather the right engine he elected to land with full flaps and gear down after a straight-in approach. As he approached the threshold a Cessna 150 taxied onto the runway. The pilot executed a go-around while trying to retract the flaps and gear electrically without results. The passenger was attempting to retract the gear manually when the aircraft struck a tree. The pilot stated he did not make his landing intentions known on unicom during the approach. No pre-impact discrepancies were found to preclude normal prop operation. Normal elect power is halved with one generation inoperative.
Probable cause:
Occurrence #1: loss of engine power(total) - non mechanical
Phase of operation: cruise - normal
Findings
1. (f) engine assembly - vibration
2. (f) in-flight planning/decision - improper - pilot in command
3. (f) propeller system/accessories,feathering system - undetermined
----------
Occurrence #2: in flight collision with terrain/water
Phase of operation: go-around (VFR)
Findings
4. (c) procedures/directives - disregarded - pilot in command
5. (c) radio communications - not used - pilot in command
6. (f) object - aircraft moving on ground
7. (f) aborted landing - performed - pilot in command
8. (f) go-around - initiated - pilot in command
9. (f) electrical system - output low
10. (f) gear retraction - not attained - pilot in command
11. (f) raising of flaps - not attained - pilot in command
12. (f) aircraft performance,engine out capability - deteriorated
13. (f) airspeed (VMC) - not attained - pilot in command
14. Object - tree(s)
Final Report:

Crash of a Cessna 411 in Vineland: 4 killed

Date & Time: May 9, 1980 at 1453 LT
Type of aircraft:
Operator:
Registration:
N4973T
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Bridgeport – Washington DC – Atlantic City
MSN:
411-0193
YOM:
1966
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
652
Circumstances:
While in cruising altitude, one of the engine failed. The pilot lost control of the airplane that stalled and entered a spin. It crashed in a field located near Vineland and exploded on ground. All four occupants were killed.
Probable cause:
Powerplant failure for undetermined reasons. The following contributing factors were reported:
- The pilot failed to maintain flying speed,
- Complete failure on one engine,
- Emergency circumstances unknown/not reported.
Final Report:

Crash of a Piper PA-61P Aerostar in Teterboro: 3 killed

Date & Time: Nov 16, 1979 at 1215 LT
Operator:
Registration:
N8099J
Flight Phase:
Survivors:
No
Schedule:
Teterboro - State College
MSN:
61P-05917963261
YOM:
1979
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
8300
Circumstances:
Shortly after takeoff from runway 24 at Teterboro Airport, while climbing, one of the engine caught fire after the exhaust pipe separated. The pilot lost control of the airplane that crashed in flames in Carlstadt, less than 1,2 mile from the runway end. The aircraft was destroyed and all three occupants were killed.
Probable cause:
Engine fire or explosion during initial climb after the pilot attempted operation with known deficiencies in equipment. The following contributing factors were reported:
- Exhaust system: stacks,
- Fatigue fracture,
- Fire in engine,
- Separation in flight,
- Exhaust pipe assembly part n° 32006-511 failed at flange weld.
Final Report:

Crash of a De Havilland DHC-6 Twin Otter 200 in Wildwood: 4 killed

Date & Time: Dec 12, 1976 at 2326 LT
Registration:
N101AC
Survivors:
Yes
Schedule:
Philadelphia - Atlantic City - Wildwood
MSN:
262
YOM:
1969
Flight number:
AL977
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
7428
Captain / Total hours on type:
5200.00
Copilot / Total flying hours:
4306
Copilot / Total hours on type:
282
Circumstances:
About 2326LT on December 12, 1976, an Atlantic City Airlines, Inc., De Havilland DHC-6 Twin Otter (N101AC) operating as Allegheny Commuter Flight 977, crashed about 4,000 feet short of the approach end of runway 19 at Cape May County Airport, New Jersey. The flight was making a VOR approach to runway 23 with a circle to land on runway 19. Of the 10 persons aboard, 4 died of injuries received in the crash. The aircraft was destroyed. About 10 minutes before the accident, according to official observation logs, at Cape May County Airport the sky was obscured with a 400 feet indefinite ceiling; the visibility was 1 mi in fog; and the wind was from 250° at 6 kns. Visibility was 1 mi to the south and west and 1 1/2
mi to the east and north.
Probable cause:
The flight crew's lack of altitude awareness during a circling approach permitting the aircraft's flight path to deviate below a safe approach profile. The aircraft's rate of descent and descent flight path angle increased as a result of windshear encountered during visual approach below minimum descent altitude. The flight crew did not recognize these flight path deviations because they were relying on visual references which were degraded by non-homogeneous fog and on kinesthetic cues which were adversely affected by the aircraft's forward centre of gravity resulting from the improperly loaded aircraft. Contributing to the accident was the lack of company procedures requiring altitude-callouts during the visual portion of an approach.
Final Report: