NICEVILLE, FL, USA
N57648
Bellanca 8KCAB
The pilot stated that while climbing after banner pickup, the aircraft began a strange vibration and aileron control seemed sloppy. He turned back to the airport and planned to drop the banner if the problems cleared up. The problems continued and he did not drop the banner. As he approached the runway he applied full engine power in an attempt float in until the banner settled. The float did not occur and the aircraft landed hard. Postcrash examination of the aircraft by an FAA inspector and wreckage recovery personnel showed no evidence of precrash failure or malfunction of the aircraft flight controls, structure, or engine.
On August 25, 2000, about 1245 central daylight time, a Bellanca 8KCAB, N57648, registered to an individual, crashed at Ruckel Airport, Niceville, Florida, while on a Title 14 CFR Part 91 banner towing flight. Visual meteorological conditions prevailed at the time and no flight plan was filed. The aircraft received substantial damage and the commercial-rated pilot received minor injuries. The flight was originating at the time of the accident. The pilot stated he departed on runway 36, flew out about 3/4 of a mile, circled back toward the airport, and entered left base to pick up a banner. He turned on final approach for banner pickup, and established airspeed at 80 mph and a 20-30 degree approach angle. He caught the ropes and started a climb. The banner engaged at about 200 feet agl. He then relaxed the pitch attitude and turned slightly to the left. He headed to the southeast and established airspeed at 55 mph. He then pulled the nose up to start a climb and then felt a strange vibration, similar to wing flaps being lowered. Airspeed also bled down to about 45 mph. He lowered the nose and checked the banner, which looked normal. He applied full engine power and the ailerons seemed sloppy. Small changes would cause the aircraft to pitch and roll inconsistently. Gaining airspeed did not improve the situation. He turned right back toward the runway. The elevator and rudder were responding properly. He planned to release the banner as he descended below the tree line if the control problems cleared up. The control problems did not clear up and he elected to land with the banner. He then turned to the left and lined up for a landing on runway 18. He was near the end of runway 18, and as he rotated, he added full engine power trying to float in till the banner settled to the ground. The float never occurred and the aircraft landed hard and collapsed the landing gear. The right wing struck the ground and the aircraft nosed down. The banner equipment was intact after the accident. A witness stated that after picking up the banner, the pilot initiated a right turn back toward the airport as if he was going to drop the banner or land. The aircraft was in a position where there was not a lot of runway distance remaining. The pilot did not release the banner and kept the airplane in a level attitude until it was a few feet above the ground. The aircraft then made a left turn of about 20-25 degrees, flared, and stalled, with a more vertical descent. The left wing appeared to be lower at this point and the aircraft hit and bounced one time. Another witness stated that when the aircraft was about 15 feet above the runway in the landing flare, the aircraft turned a little to the left and the nose dropped slightly. The aircraft descended and hit left wing first and then bounced onto the right wing. Postcrash examination of the aircraft by an FAA inspector and wreckage recovery personnel showed no evidence of precrash failure or malfunction of the aircraft flight controls, structure, or engine.
The pilots failure to drop the advertising banner prior to a precautionary landing resulting in the aircraft stalling and landing hard. Contributing to the accident was the pilots failure to maintain airspeed during climb after banner pickup resulting in the aircraft entered the early stages of a stall, and the pilots failure to recognize the early stages of a stall and initiate recovery.
Source: NTSB Aviation Accident Database
Aviation Accidents App
In-Depth Access to Aviation Accident Reports
