Test

The multiengine airplane had not been flown for about 4 months and was being prepared for export. The pilot was attempting a local test flight after avionics upgrades had been performed. Shortly after takeoff, the pilot transmitted that he was experiencing an "emergency"; however, he did not state the nature of the emergency. The airplane was observed experiencing difficulty climbing and entered a right turn back toward the airport. It subsequently stalled, rolled right about 90 degrees, and descended. The airplane impacted several parked vehicles and came to rest inverted. A postcrash fire destroyed the airframe. Both engines were destroyed by fire and impact damage. The left propeller assembly was fire damaged, and the right propeller assembly remained attached to the gearbox, which separated from the engine. Examination of wreckage did not reveal any preimpact malfunctions. It was noted that the left engine displayed more pronounced rotational signatures than the right engine, but this difference could be attributed to the impact sequence. The left propeller assembly displayed evidence of twisting and rotational damage, and the right propeller assembly did not display any significant evidence of twisting or rotational damage indicative of operation with a difference in power. The lack of flight recorders and the condition of the wreckage precluded the gathering of additional relevant information.

The pilot stated that, during the preflight inspection of the airplane, he checked the fuel gauge, and it indicated 65 gallons. Due to the design of the fuel system, it is not possible to visually check the fuel level to confirm that the fuel gauge indication is accurate. During takeoff and as he reduced power for enroute climb, the left engine began to surge and lose power. He immediately turned left back toward the airport and contacted the control tower to advise that he was making a single-engine, straight-in approach to land. When he lowered the landing gear, the right engine began to surge and lose power. Subsequently, the pilot declared an emergency, and, realizing he had insufficient engine power and altitude to return to the airport, he retracted the landing gear and made a no-flap, gear-up landing on a nearby golf course. Postaccident application of battery power to the airplane confirmed that the fuel gauge indicated 65 gallons; however, when the airplane's fuel system was drained, only about 1/2 gallon of fuel was recovered. Thus, the engines lost power due to fuel exhaustion.

The aircraft, registered to the United States Customs Service, and operated by Stevens Aviation, Inc., was substantially damaged during collision with a deer after landing on Runway 9 at Greenwood County Airport (GRD), Greenwood, South Carolina. The airplane was subsequently consumed by postcrash fire. The two certificated airline transport pilots were not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the maintenance test flight, which was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. According to the pilot, the purpose of the flight was to conduct a test of the autopilot and flight director systems on board the airplane, following a "cockpit modernization" their company had performed. The airplane completed the NDB/GPS RWY 27 instrument approach procedure and then circled to land on Runway 9. About 5 seconds into the landing rollout, a deer appeared from the wood line and ran into the path of the airplane. The deer struck the airplane at the leading edge of the left wing above the left main landing gear, and ruptured an adjacent fuel cell. The pilot was able to maintain directional control, and the airplane was stopped on the runway, spilling fuel and on fire. The crew performed an emergency shutdown of the airplane and egressed without injury.Greenwood County Airport did not have a fire station co-located on the airport facility. The fixed base operator called 911 at the time of the accident, and the fire trucks arrived approximately 10 minutes after notification.

According to a friend of the pilot, the pilot was taking the airplane to have an annual inspection completed. The friend assisted the pilot before departure and watched as the airplane departed. He did not notice any anomalies with the airplane during the takeoff or the climbout. According to a witness in the vicinity of the accident site, he heard the airplane coming toward him, and it was flying very low. He looked up and saw the airplane approximately 200 feet over his house and descending toward the trees. As he watched the airplane, he noticed that the right propeller was not turning, and the right engine was not running. He stated that the left engine sounded as if it was running at full power. The airplane pitched up to avoid a power line and rolled to the right, descending below the tree line. A plume of smoke and an explosion followed. Examination of the right propeller assembly revealed evidence of significant frontal impact. The blades were bent but did not have indications of rotational scoring; thus they likely were not rotating at impact. One preload plate impact mark indicated that the blades were at an approximate 23-degree angle; blades that are feathered are about 86 degrees. Due to fire and impact damage of the right engine and related system components, the reason for the loss of power could not be determined. An examination of the airframe and left engine revealed no mechanical malfunctions or failures that would have precluded normal operation. A review of the airplane maintenance logbooks revealed that the annual inspection was 12 days overdue. According to Lycoming Service Instruction No. 1009AS, the recommended time between engine overhaul is 1,200 hours or 12 years, whichever occurs first. A review of the right engine maintenance logbook revealed that the engine had accumulated 1,435 hours since major overhaul and that neither engine had been overhauled within the preceding 12 years. Although the propeller manufacturer recommends that the propeller be feathered before the engine rpm drops below 1,000 rpm, a review of the latest revision of the pilot operating handbook (POH) revealed that the feathering procedure for engine failure did not specify this. It is likely that the pilot did not feather the right propeller before the engine reached the critical 1,000 rpm, which prevented the propeller from engaging in the feathered position

On June 8, 2012, about 1307 central daylight time, a Piper PA-31-325, N174BH, departed from the South St Paul Municipal Airport-Richard E Fleming Field (SGS), South St Paul, Minnesota for a maintenance test flight. The airplane reportedly had one of its two engines replaced and the pilot was to fly for about 4 hours to break-in the engine. The airplane did not return from the flight and was reported overdue. The airplane is missing and is presumed to have crashed. The airline transport pilot has not been located. The airplane was registered to Family Celebrations LLC, and was operated as a 14 Code of Federal Regulations Part 91 personal flight. Visual meteorological conditions prevailed and no flight plan was filed. The flight departed SGS with the intention of returning to SGS at the conclusion of the flight. The airplane was reported missing and an alert notification issued about 2225. The last reported contact with the airplane and pilot was about 1300 when the fixed base operator at SGS towed the airplane to the fuel pumps. When he returned about 15 minutes later, the airplane was no longer there. Aircraft radar track data from various ground based sources indicated that the airplane departed SGS about 1307. The airplane maneuvered east of SGS before turning toward the north. The airplane's track continued north toward Duluth, Minnesota. Once the airplane reached Duluth, it followed the west shoreline of Lake Superior. Radar track data indicated that the airplane was at a pressure altitude of 2,800 feet when it reached the shoreline. The airplane continued along the west shoreline toward Two Harbors, Minnesota, flying over the water while maintaining a distance of about 0.5 miles from the shore. As the airplane approached Two Harbors, it descended. The airplane's last recorded position at 1427 was about 30 miles northeast of Duluth, Minnesota, at an uncorrected pressure altitude of 1,600 feet. The Air Force Rescue Coordination Center coordinated a search for the missing airplane. The Civil Air Patrol, United States Coast Guard, and other entities participated in the search efforts. Search efforts were suspended on July 4, 2012.

The aircraft departed Mexicali Airport with one pilot on board. The goal of the flight was a test experiment on behalf of the Mexican Civil Aviation Authority and various agencies to crash deliberately the aircraft in the Laguna Salada for a television program organized by British, German, Mexican and American Producers. While approaching the desert along the Mexican 5 Highway, about 30 km southwest of Mexicali, the pilot bailed out and the aircraft continued for few seconds in a slightly flat attitude. In a flaps down and gear down configuration, the aircraft touched down hard in a sandy area, lost its undercarriage, crashed and came to rest, broken in two.

The airplane, registered to SV Leasing Company of Florida, operated by SOCATA North America, Inc., sustained substantial damage during a forced landing on a highway near Hollywood, Florida, following total loss of engine power. Visual meteorological conditions prevailed at the time and an instrument flight rules (IFR) flight plan was filed for the 14 Code of Federal Regulations (CFR) Part 91 maintenance test flight from North Perry Airport (HWO), Hollywood, Florida. The airline transport pilot and pilot-rated other crew member sustained minor injuries; there were no ground injuries. The flight originated from HWO about 1216. The purpose of the flight was a maintenance test flight following a 600 hour and annual inspection. According to the right front seat occupant, in anticipation of the flight, he checked the fuel load by applying electrical power and noted the G1000 indicated the left fuel tank had approximately 36 gallons while the right fuel tank had approximately 108 gallons. In an effort to balance the fuel load with the indication of the right fuel tank, he added 72.4 gallons of fuel to the left fuel tank. At the start of the data recorded by the G1000 for the accident flight, the recorded capacity in the left fuel tank was approximately 105 gallons while the amount in the right fuel tank was approximately 108 gallons. The PIC reported that because of the fuel load on-board, he could not see the level of fuel in the tanks; therefore, he did not visually check the fuel tanks. By cockpit indication, the left tank had approximately 105 gallons and the right tank had approximately 108 gallons. The flight departed HWO, but he could not recall the fuel selector position beneath the thrust lever quadrant. He further stated that the fuel selector switch on the overhead panel was in the "auto" position. After takeoff, the flight climbed to flight level (FL) 280, and levelled off at that altitude about 20 minutes after takeoff. While at that altitude they received a "Fuel Low R" amber warning CAS message on the G1000. He checked the right fuel gauge which indicated 98 gallons, and confirmed that the fuel selector automatically switched to the left tank. After about 10 seconds the amber warning CAS message went out. He attributed the annunciation to be associated with a failure or malfunction of the sensor, and told the mechanic to write this issue down so it could be replaced after the flight. The flight continued and they received an amber warning CAS message, "Fuel Unbalance" which the right fuel tank had more fuel so he switched the fuel selector to supply fuel from the right tank to the engine. The G1000 indicates they remained at that altitude for approximately 8 minutes. He then initiated a quick descent to 10,000 feet mean sea level (msl) and during the descent accelerated to Vmo to test the aural warning horn. They descended to and maintained 10,000 feet msl for about 15 minutes and at an unknown time, they received an amber warning CAS message "Fuel Low R." Once again he checked the right fuel gauge which indicated it had 92 gallons and confirmed that the fuel tank selector automatically switched to the left tank. After about 10 seconds the CAS message went out. Either just before or during descent to 4,000 feet, they received an amber CAS message "Fuel Unbalance." Because the right fuel gauge indicated the fullest tank was the right tank, he switched the fuel selector to supply fuel to the engine from the right tank. The flight proceeded to the Opa-Locka Executive Airport, where he executed an ILS approach which terminated with a low approach. The pilot cancelled the IFR clearance and proceeded VFR towards HWO. While in contact with the HWO air traffic control tower, the flight was cleared to join the left downwind for runway 27L. Upon entering the downwind leg they received another amber CAS message "Fuel Unbalance" and at this time the left fuel gauge indicated 55 gallons while the right fuel gauge indicated 74 gallons. Because he intended on landing within a few minutes, he put the fuel selector to the manual position and switched to the fullest (right) tank. Established on final approach to runway 27L at HWO with the gear down, flaps set to landing, and minimum speed requested by air traffic for separation (85 knots indicated airspeed). When the flight was at 800 feet, the red warning CAS message "Fuel Press" illuminated and the right seat occupant with his permission moved the auxiliary fuel boost pump switch from "Auto" to "On" while he, PIC manually moved the fuel selector to the left tank. In an effort to restore engine power he pushed the power lever and used the manual over-ride but with no change. Assured that the engine had quit, he put the condition lever to cutoff, the starter switch on, and then the condition lever to "Hi-Idle" attempting to perform an airstart. At 1332:42, a flight crew member of the airplane advised the HWO ATCT, "…just lost the engine"; however, the controller did not reply. The PIC stated that he looked to his left and noticed a clear area on part of the turnpike, so he banked left, and in anticipation of the forced landing, placed the power lever to idle, the condition lever to cutoff, the fuel tank selector to off, and put the electrical gang bar down to secure the airplane's electrical system. He elected to retract the landing gear in an effort to shorten the landing distance. The right front seat occupant reported that the airplane was landed in a southerly direction in the northbound lanes of the Florida Turnpike. There were no ground injuries.

A technician was in charge to ferry the airplane to a hangar for a maintenance control. While taxiing, the Falcon went out of control, rolled down an embankment and collided with a utility pole. The nose was severely damaged and the aircraft was damaged beyond repair. According to the technician, who escaped uninjured, the brakes failed while taxiing.

The twin engine aircraft was engaged in a local post maintenance test flight at Monterrey-Del Norte Airport. Shortly after takeoff, the airplane encountered difficulties to gain height when it stalled and crashed in a field located 500 metres past the runway end, bursting into flames. The aircraft was destroyed by fire and both occupants were killed.

On 24th May, 2011 at 11:54 h, a Beechcraft C90 aircraft with nationality and registration marks N364UZ, operated by Shoreline Energy International Limited (SEIL), departed Old Kaduna (Military) airport on a test flight with a pilot and another person onboard with three hours fuel endurance. The test flight was on a visual flight rules (VFR) flight plan. According to an eye witness, the aircraft sound was unusual and the aircraft seemed not to be gaining altitude after takeoff. Another eye witness (a local farmer), stated that he saw the aircraft moving up and down with increasing and decreasing engine sound. Thereafter, the aircraft impacted a mango tree, turned and crashed. The local farmer further stated that he and some military personnel tried all they could to rescue the occupants inside the aircraft but their efforts were not successful. At 11:59 h, the aircraft crashed on a farm-land 878 meters short of RWY 23 (military) and engulfed into flames. The two occupants were fatally injured. Dornier Aviation Nigeria AIEP (DANA) and Nigerian Air Force (NAF) fire-fighting personnel were dispatched immediately. There was no direct access between the runway and the accident site, which delayed the fire trucks from reaching the aircraft at accident site on time. The accident occurred in day light, in visual meteorological conditions (VMC).