Texas

The pilot was engaged in a five-hour aerial photography mission. While returning to Victoria Airport, he encountered engine trouble and attempted an emergency landing when the airplane crashed on Mockingbird Lane and a feeder road to Zac Lentz Parkway, also known as State Highway Loop 463, Victoria, Texas. The aircraft was destroyed as well as several cars. The pilot and four people on the ground were injured, one seriously.

The crew was completing a flight from Odessa to Ellington Field, near Houston. After takeoff from runway 16, while in initial climb, the twin engine airplane collided with a poweline located about 270 metres past the runway end. The airplane descended to the right and crashed onto a garage located 150 metres further, bursting into flames. The airplane was totally destroyed and both occupants were killed.

Shortly after takeoff from McKinney Airport, while in initial climb, the twin engine airplane entered an uncontrolled descent and crashed inverted in a quarry, bursting into flames. Two people were killed and a third occupant was seriously injured. It is believed that the pilot encountered engine problems shortly after departure.

While on final approach to San Angelo-Mathis Field, the single engine airplane entered a rapid descent with a rate of 5,058 feet per minute then crashed in an open field located about 12 km south of the airport. The airplane was totally destroyed and both occupants were killed.

While climbing the airplane to cruise altitude after takeoff, the pilot observed an increase in engine oil temperature above the normal range and requested to return to the departure airport. While receiving vectors for an instrument approach, the pilot saw smoke in the cabin and the engine lost total power. Unable to glide to any runway, the pilot selected a field for the forced landing, during which the airplane sustained substantial damage to the wings and fuselage. Postaccident examination revealed that about 2 quarts of oil remained in the engine, and the recovered oil displayed evidence of metal contamination. There was evidence of an oil leak in the engine compartment and along the lower fuselage. There was evidence of a crankcase fracture near the oil dip stick port; however, a laboratory examination determined the fracture to be consistent with overload and likely due to impact-related damage. The engine exhibited no evidence of any loose or disconnected oil lines. The oil filter was removed, and the filter material was found to be saturated with metallic particles. The oil suction screen plug, located on the oil sump, was not secured with safety wire as required per the manufacturer’s maintenance manual. There was no evidence that the plug or required safety wire was damaged by other objects. The oil suction screen plug was found to be loose, with engine oil observed below the oil suction screen plug. The crush washer behind the oil screen plug was intact and exhibited no damage. Laboratory analysis of the metallic debris recovered from the oil suction screen was consistent with connecting rod material as well as steel from fittings, fasteners, and brackets. The metallic debris found in the recovered oil, oil filter, and oil suction screen was likely due to mechanical damage associated with oil starvation. Eleven days before the accident flight, the pilot observed decreased engine manifold pressure and a partial loss of engine power. He diverted to an airport, where he had the turbocharger replaced by an aviation mechanic. In addition to replacing the turbocharger, the mechanic also drained and replaced the engine oil, which included removal and reinstallation of the oil suction screen plug. The loss of engine power was likely due to a loss of oil during the flight that led to oil starvation within the engine. The loose oil suction screen plug, the absence of safety wire on the plug, and the evidence of an oil leak beneath the plug were consistent with the mechanic’s failure to properly secure the oil suction screen plug during recent maintenance.

The pilot was landing at the destination airport with a gusting crosswind. Upon touchdown, he established the aileron controls for the crosswind and applied the brakes; however, no braking action was observed. The airplane subsequently drifted left and departed the runway pavement. It came to rest upright in the grass infield area adjacent to the runway. The outboard portion of the right wing separated which resulted in substantial damage. Data indicated that the airplane was 14 knots or more above the published landing reference speed when it crossed the runway threshold, and it touched down about 2,000 ft from the threshold. The left and right weight-on-wheels (WOW) parameters transitioned from air to ground consistent with initial touchdown; however, the left WOW parameter transitioned back to air about 2 seconds later. The right WOW parameter remained on ground until the airplane departed the runway pavement. A detailed review of the Central Maintenance Function (CMF) data files did not reveal any record of airplane system anomalies from the time the airplane lifted off until it touched down. Multiple system anomalies were recorded after the runway excursion consistent with airframe damage sustained during the accident sequence. The brake system touchdown protection is designed to prevent brake application until wheel spin-up occurs to avoid the possibility of inadvertently landing with a locked wheel due to brake application. After weight-on-wheels has been true for three seconds, power braking is enabled. It is likely that the lack of positive weight-on-wheel parameters inhibited brake application due to the touchdown protection function and resulted in the pilot not observing any braking action. The excess airspeed, extended touchdown, and transient weight-on-wheels parameters were consistent with the airplane floating during the landing flare and with the application of aileron controls for the crosswind conditions. The airplane was not equipped with wing-mounted speed brakes which would have assisted in maintaining weight-on-wheels during the initial portion of the landing. The most recent wind report, transmitted by the tower controller when the airplane was on a 3- mile final, presented a 70° crosswind at 15 knots, gusting to 25 knots. The corresponding crosswind gust component was about 24 knots. The airplane flight manual specified a crosswind limitation of 20 kts for takeoff and landing; therefore, the crosswind at the time of the accident exceeded the airframe crosswind limitation and would have made control during touchdown difficult. The pilot reported that he had made two requests with the approach controller to land on a different runway, but those requests were denied. The investigation was unable to make any determination regarding a pilot request for an alternate runway. Federal Aviation Regulations stated that the pilot in command of an aircraft is directly responsible for, and is the final authority as to, the operation of that aircraft. The regulations also stated that no person may operate a civil aircraft without complying with the operating limitations. The pilot’s ultimate acceptance of the runway assignment which likely exceeded the crosswind limitation of the airplane was contrary to the regulations and to the safe operation of the airplane.

Following an uneventful flight from Memphis at FL260, the pilot initiated the descent to Yoakum Airport, Texas. On final approach to runway 31, the single engine airplane went out of control and crashed in an open field located about one mile southeast of the airfield. A passenger was able to get out from the cabin and was slightly injured while all four other occupants were killed.

The twin engine airplane departed Denton Enterprise Airport runway 36 at 1459LT and continued to the west at an altitude of 2,000 feet. Eight minutes later, the pilot initiated a left hand circuit to land at Decatur Airport. While descending on final, the speed decreased and the airplane crashed nearby a wooded area located 6 km short of runway 35. The aircraft was destroyed and the pilot, sole on board, was killed.

The Boeing B-17 was taking part to an airshow at Dallas-Executive (Redbird) Airport, carrying five people. While passing over the airfield at a relative low altitude, it collided with a Bell P-63 Kingcobra that was engaged in the same manoeuvre and coming from its left. The B-17 was cut in two, entered an uncontrolled descent and crashed in a field, bursting into flames. The P-63 was also destroyed. All six people in both aircraft were killed. At the time of the collision, the B-17 was following a straight-in course while the P-63 was supposed to cut its trajectory behind. Obviously, the pilot of the P-63 misjudged the situation.

The pilot reported that, before the flight, the airplane was fueled with 140 gallons of Jet A fuel. Shortly after takeoff, both engines lost total power. Because the airplane had insufficient altitude to return to the airport, the pilot executed a forced landing to a field and the left wing sustained substantial damage. A postcrash fire ensued. The investigation determined that the airplane was inadvertently fueled with Jet A fuel rather than AVGAS, which was required for the airplane’s reciprocating engines. The line service worker who fueled the airplane reported that there were no decals at the airplane fuel ports; however, postaccident examination of the airplane found that a decal specifying AVGAS was present at the right-wing fuel port. The investigation could not determine whether the same or a similar decal was present at the left-wing fuel port because the left wing was partially consumed during the postimpact fire.