Old Bridge, NJ, USA
N8446F
Piper PA-34-200T
According to radar data and witnesses, the airplane entered the airport traffic pattern and attempted to land on the runway. The pilot then executed a go-around, performed a climbing right turn, and impacted trees and terrain shortly thereafter. The weather conditions reported around time of the accident included 1/8 to 1/4 mile visibility in fog. The pilot did not hold an instrument rating. Examination of the wreckage revealed no evidence of any preimpact malfunctions. With regard to night-flight in poor or marginal weather conditions, the FAA Airplane Flying Handbook FAA-H-8083-3 states, "The pilot flying under [visual flight rules] VFR must exercise caution to avoid flying into clouds or a layer of fog.… Remember that if a descent must be made through fog, smoke, or haze in order to land, the horizontal visibility is considerably less then when looking through the restriction than it is when looking straight down through it from above. Under no circumstances should a VFR night-flight be made during poor or marginal weather conditions unless both the pilot and the aircraft are certificated and equipped for flight under instrument flight rules (IFR)."
HISTORY OF FLIGHT On March 12, 2006, about 2220 eastern standard time, a Piper PA-34-200T, N8446F, was destroyed when it impacted trees and terrain while maneuvering near Old Bridge Airport (3N6), Old Bridge, New Jersey. The certificated private pilot and one passenger were fatally injured, and two additional passengers were seriously injured. Night instrument meteorological conditions prevailed, and no flight plan was filed for the flight that departed from Grand Strand Airport (CRE), North Myrtle Beach, South Carolina, at 1934. The personal flight was conducted under 14 CFR Part 91. According to radar data obtained from the Federal Aviation Administration (FAA), a radar target correlated to be the accident airplane approached Old Bridge Airport from the southwest. The target maneuvered consistent with entering the airport traffic pattern on a left downwind leg to land on runway 24. The target continued in the traffic pattern, descending to 400 feet msl on the final leg of the approach, where radar contact was lost about 1/2 mile from the runway threshold. No further radar targets were observed. A witness, located about 1/2 mile south of the airport, heard the accident airplane fly over her house at a "very low" altitude, heading in an easterly direction. The airplane then turned toward runway 24, and "dipped down" at a point about halfway down the runway. She initially thought that the airplane might land, but then saw the airplane pitch upward and enter a climbing turn to the right. Another witness, located about 1 mile beyond the departure end of runway 24, saw the accident airplane as it came toward him from the runway. He heard the airplane's engines "revving," and saw the lights of the airplane coming toward him. The airplane then turned right, and disappeared from view. Shortly thereafter the witness heard the sounds of impact. The witness also noted that the weather at the time of the accident was "foggy." A review of air traffic control and flight service station communication data revealed that the pilot had not contacted any facilities prior to the accident flight, or after departing the Myrtle Beach area. The accident occurred during the hours of night at 40 degrees, 19.930 minutes north latitude, 74 degrees, 21.232 minutes west longitude. PERSONNEL INFORMATION The pilot held a private pilot certificate with ratings for airplane single and multiengine land. He did not hold an instrument rating. His most recent FAA third class medical certificate was issued on August 10, 2005, and on that date he reported 1,657 total hours of flight experience. AIRCRAFT INFORMATION The airplane's most recent annual inspection was completed on January 10, 2006, and at that time the airplane had accumulated 4,027 total hours of flight time. The airplane had accumulated an additional 18 hours of flight time since that date. METEOROLOGICAL INFORMATION The weather reported at Belmar-Farmingdale Airport (BLM), Belmar, New Jersey, about 14 nautical miles southeast of Old Bridge Airport, at 2215, included winds from 280 degrees at 4 knots, an overcast ceiling at 100 feet, less than 1/4 statute mile visibility, temperature 48 degrees Fahrenheit, dewpoint 46 degrees Fahrenheit, and an altimeter setting of 30.04 inches of mercury. A witness reported that he was driving on a road adjacent and perpendicular to the departure end of runway 24, about 10 minutes prior to the accident. He reported that when he typically drove down the road, he would always look down the airport runway. On the night of the accident, he could see that the airport beacon and runway lights were illuminated; however, he could only see about halfway down the runway due to the weather conditions. He reported that the horizontal visibility was "really bad," and estimated it to be about 1/8 mile in fog. AIRPORT INFORMATION Old Bridge Airport had a single 3,594-foot by 50-foot runway oriented in a 06/24 configuration. WRECKAGE AND IMPACT INFORMATION The airplane came to rest in a wooded area, about 1/2 mile northwest of the airport. The initial impact point was a tree, about 50 feet tall. The wreckage path was about 350 feet long, and oriented in a direction of 040 degrees magnetic. The right wing flap was located at the base of the tree, and portions of the aileron cables from the right wing were located in the tree. Various airplane parts were located along the wreckage path, including portions of both wing tips, small portions of the vertical stabilizer and stabilator, and the nose of the airplane. Numerous broken tree trunks and branches were also dispersed along the wreckage path. The right wing, including the right engine and cowling, was located about 30 feet west of the main wreckage, and the outermost portion of the wing was consumed by fire. The left wing was partially separated from the fuselage near the wing root, and remained connected by the aileron cable, engine control cables, and wire bundles. The aft portion of the fuselage was almost completely separated from the main fuselage, and was folded underneath so that the vertical stabilizer was pointing downward and the leading edges of the stabilator and vertical stabilator were pointing rearward. The vertical stabilizer was also partially detached from the aft fuselage. The aft fuselage remained attached to the forward fuselage by a small amount of fuselage skin and the stabilator control cables. The vertical stabilizer and stabilator were separated from the fuselage, but remained attached by their respective control cables. Control cable continuity was confirmed from the stabilator and left aileron to the cabin area. The right aileron cable, rudder control cables, rudder trim cables, and stabilator trim cables were severed, and exhibited signatures consistent with overload failure. The flap control handle was observed in the 10-degree detent; however, the flap position could not be confirmed due to impact damage. The landing gear position selector was destroyed by impact forces. The left main landing gear was down, and the actuator was fully extended and separated from the landing gear strut. One end of the actuator remained attached to the inboard section of the left wing spar, which remained attached to the fuselage center-section. The right main landing gear was collapsed and dislodged from its well. The nose landing gear was separated from the fuselage, and was located about 5 feet from the main wreckage. Examination of the cabin interior revealed that none of the seat belt buckles were fastened, and that the aft facing, co-pilot side passenger seat had been removed prior to the accident flight. The left engine crankshaft was rotated via the accessory section, and continuity was confirmed throughout the powertrain. Compression was obtained on all six cylinders. Borescope examination of all six cylinders revealed no anomalies. The turbocharger was rotated by hand, and was free of any impediment to movement. Examination of the fuel pump and fuel manifold revealed that they contained fuel and were free of obstructions. The top six spark plugs were removed, and five of the six electrodes were light gray in color, while the number 2 cylinder electrode was white. The left magneto was damaged, and could not be rotated. Crankshaft rotation produced spark at all terminal leads of the right magneto. The left propeller had separated from its respective engine aft of the propeller flange. The propeller blades were bent opposite to the direction of rotation, and exhibited chordwise scratching and gouging. One of the blades was bent aft at about mid-span, one was bent aft about 8 inches from the blade tip and was missing the outermost 3 inches of blade tip, while the other blade was straight. The right engine crankshaft was rotated via the propeller, and continuity was confirmed throughout the powertrain and the accessory section. Compression was obtained on all six cylinders. Borescope examination of all six cylinders revealed no anomalies. The turbocharger was rotated by hand, and was free of any impediment to movement. Examination of the fuel pump and fuel manifold revealed that they contained fuel, and were free of obstructions. The top six spark plugs were removed, and all of the electrodes were gray in color. Crankshaft rotation produced spark at all of the top spark plug terminal leads. The right propeller remained attached to its respective engine. All three propeller blades were twisted perpendicular to the plane of rotation, and were bent opposite to the direction of rotation. The blades exhibited s-bending, and chordwise scratching and gouging. In addition, the outboard 3 inches of blade tip were missing from all three blades. The vacuum pumps from both engines were removed and rotated by hand, which produced pressure and suction on the respective ports. MEDICAL AND PATHOLOGICAL INFORMATION The FAA's Bioaeronautical Sciences Research Laboratory, Oklahoma City, Oklahoma, performed toxicological testing on the pilot. ADDITIONAL INFORMATION According to the FAA Airplane Flying Handbook FAA-H-8083-3 (Chapter 10, "Night Operations"), "Night flying is very different from day flying and demands more attention of the pilot. The most noticeable difference is the limited availability of outside visual references. Therefore, flight instruments should be used to a greater degree in controlling the airplane. This is particularly true on night takeoffs and climbs.… After becoming airborne, the darkness of night often makes it difficult to note whether the airplane is getting closer to or farther from the surface. To ensure the airplane continues in a positive climb, be sure a climb is indicated on the attitude indicator, vertical speed indicator (VSI), and altimeter.… Necessary pitch and bank adjustments should be made by referencing the attitude and heading indicators. It is recommended that turns not be made until reaching a safe maneuvering altitude." The handbook later states, "Generally, at night it is difficult to see clouds and restrictions to visibility, particularly on dark nights or under overcast. The pilot flying under VFR [visual flight rules] must exercise caution to avoid flying into clouds or a layer of fog.… Remember that if a descent must be made through fog, smoke, or haze in order to land, the horizontal visibility is considerably less then when looking through the restriction than it is when looking straight down through it from above. Under no circumstances should a VFR night-flight be made during poor or marginal weather conditions unless both the pilot and the aircraft are certificated and equipped for flight under instrument flight rules (IFR)." The wreckage was released to a representative of the owner's insurance company on March 14, 2006.
The pilot's improper decision to conduct visual approach and landing in instrument meteorological conditions, and his failure to maintain adequate clearance from trees and terrain during the go-around. Factors in the accident were the low cloud ceiling and fog conditions.
Source: NTSB Aviation Accident Database
Aviation Accidents App
In-Depth Access to Aviation Accident Reports
