What happened
The pilot was conducting a takeoff from Runway 05 when he became aware of a conflict with another aircraft. The airport operator had announced over the UNICOM frequency that Runway 13 was the active runway for landing. During the initial climb-out, the pilot spotted another aircraft lined up on Runway 13, appearing to be preparing to land.
In an effort to avoid the conflicting traffic, the pilot initiated a steep climb and began scanning for the other aircraft. At an altitude of approximately 200 to 300 feet above ground level, the aircraft lost airspeed and stalled. The stall progressed into a spin, resulting in a crash landing with impact to the ground.
The investigation
The investigation focused on the flight dynamics and pilot actions during the critical phase of takeoff. Examination of the sequence of events indicated that the pilot's reaction to the visual contact with the other aircraft led to an aggressive pitch-up maneuver. This action exceeded the critical angle of attack for the aircraft at low airspeed, directly causing the aerodynamic stall.
Findings
The primary factor in this accident was the pilot's decision to perform a steep climb and visually search for conflicting traffic while operating at a very low altitude. The lack of adequate airspeed during this maneuver resulted in an unrecoverable stall and spin. The confusion regarding active runway assignments, communicated via UNICOM, contributed to the situational awareness failure.
Safety message
Pilots operating at uncontrolled airports must clearly understand which runway is active before entering the runway or beginning takeoff roll. If a conflict arises during takeoff, pilots should prioritize maintaining safe airspeed and climbing performance over visual acquisition of other traffic. Aggressive maneuvers at low altitude leave little margin for error and can lead to loss of control.