Plane crash map Locate crash sites, wreckage and more

N3900X accident description

Pennsylvania map... Pennsylvania list
Crash location 40.203889°N, 75.430000°W
Nearest city Collegeville, PA
40.185660°N, 75.451571°W
1.7 miles away
Tail number N3900X
Accident date 25 Jul 2007
Aircraft type Aero Commander 100
Additional details: None

NTSB Factual Report

On July 25, 2007, about 1448 eastern daylight time, an Aero Commander 100, N3900X, was substantially damaged when it impacted trees near Perkiomen Valley Airport (N10), Collegeville, Pennsylvania. The certificated private pilot incurred minor injuries. Visual meteorological conditions prevailed, and no flight plan was filed for the local personal flight, which was conducted under 14 Code of Federal Regulations Part 91.

Perkiomen Valley Airport was comprised of a single, asphalt runway that was 2,880 feet long by 40 feet wide. A single parallel taxiway ran along the north side of the runway, extending from the mid-field point to near the departure end of runway 9.

During a telephone interview, and in a written statement, the pilot stated that the purpose of the flight was to test fly the airplane following the completion of an annual inspection. He performed a preflight inspection of the airplane and performed a run-up check of the engine, with no discrepancies noted. He then took off from runway 9, and remained in the airport traffic pattern, before landing and taxiing back for another takeoff. The pilot initially stated that the accident occurred during the second takeoff, but later recalled that it actually occurred during the third takeoff, following a touch-and-go landing. During the initial climb of the third takeoff, about 60 to 70 feet above the ground, the engine lost partial power. The pilot applied the carburetor heat, and confirmed that the throttle was in the full forward position. He then realized that the airplane would not clear the trees beyond the departure end of the runway, so he retarded the throttle and extended the flaps fully. The airplane subsequently impacted a tree, where it came to rest.

A flight instructor and a student observed the accident airplane as it flew in the airport traffic pattern, and witnessed the accident. During separate telephone interviews, they each recounted a similar series of events. According to the flight instructor, he and his student had flown to N10 in order to practice short and soft field takeoffs and landings. After entering the traffic pattern, they performed a full stop landing, due to the "short" length of the runway. They then taxied back, took off, and watched as the accident airplane taxied, departed behind them, and also remained in the airport traffic pattern. The flight instructor noted that he did not hear the accident pilot make any position announcements over the radio as he flew.

After landing for a second time, the flight instructor and the student again back-taxied on the runway for another takeoff. As they taxied, they noticed the accident airplane on final approach to the runway, and got the impression that the accident pilot was not going to abort his landing attempt. The flight instructor told the student to exit the runway, onto the grass, while the accident airplane landed. The flight instructor and student again departed, and remained in the airport traffic pattern, followed by the accident airplane.

After again landing and taxiing back, the flight instructor and the student sat on the taxiway and watched the accident airplane as it approached the runway. Everything about the approach appeared normal, until the accident airplane flared, and "ballooned." The nose of the airplane then came down and the airplane ballooned again at about the mid-field point, before it ballooned a third time. The airplane's nose then "abruptly" pitched down, the airplane touched down "hard," bounced, departed the end of the runway, and struck trees.

Another witness, who was driving on a road that ran perpendicular to the departure end of the runway, stated that she saw the accident airplane as it was coming down the runway. She stated that the airplane was "bumping" down the runway. She recalled that the way the airplane bounced down the runway reminded her of a relative, who was a student pilot, and used to bounce landings. As the airplane traveled towards the end of the runway, she thought it was taking off because of the direction it was headed in, but that it would not clear the trees at the end of the runway. The airplane then departed the end of the runway, while still on the ground, then "came up into the air a little," but not enough to clear the trees. She could not hear any engine sounds as her windows were up and the air conditioning was on at the time.

After the airplane was recovered from a tree, it was examined by a Federal Aviation Administration (FAA) inspector. During the examination the inspector confirmed the continuity of the flight controls, and found that they were free to move and were properly connected. Additionally, the engine controls were also properly connected and free to move. Examination of fuel samples taken from both wing fuel tanks, and from the carburetor sump drain, revealed that they were absent of water or debris. Rotation of the engine crankshaft produced compression on all four cylinders. Six quarts of oil remained in the engine oil sump.

The pilot held a private pilot certificate with a rating for airplane single engine land. The pilot's most recent application for an FAA third class medical certificate was dated December 2004, and at that time he reported 250 total hours of flight experience.

The weather conditions reported at Pottstown Limerick Airport (PTW), Pottstown, Pennsylvania, about 6 nautical miles west of the accident site, at 1454, included winds from 200 degrees at 9 knots, 10 statute miles visibility, scattered clouds at 7,500 feet, temperature 29 degrees Celsius, dewpoint 16 degrees Celsius, and an altimeter setting of 30.15 inches of mercury.

NTSB Probable Cause

The pilot's inadequate recovery from a bounced landing.

© 2009-2020 Lee C. Baker / Crosswind Software, LLC. For informational purposes only.