11 May 2018: KOLB FIRESTAR II

11 May 2018: KOLB FIRESTAR II (N9216E) — Unknown operator

No fatalities • Atmore, AL, United States

Probable cause

The noncertificated pilot's failure to maintain airplane control, which resulted in an aerodynamic stall. Contributing to the accident was the pilot's lack of flight experience and qualification.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHTOn May 11, 2018, about 1203 central daylight time, an experimental amateur-built Kolb Firestar 2 airplane, N9216E, sustained substantial damage when it impacted a tree and terrain near Atmore, Alabama. The non-certificated pilot was seriously injured. The airplane was registered to and operated by the pilot as a Title 14 Code of Federal Regulations Part 91 personal flight. Visual meteorological conditions prevailed at the time of the accident and no flight plan was filed. The local flight had departed Atmore Municipal Airport (OR1), Atmore, Alabama about 13 minutes prior to the accident.

According to the pilot, he was in cruise flight at an altitude of about 600 ft above ground level (agl) when the airplane began "swaying left and right;" the pilot clarified that the airplane was "not yawing or rolling." He was unable to get the airplane "to straighten out," so he began a descent. When it was about 40 ft agl, the airplane struck a tree, and then a powerline, and then impacted the ground.

The airplane came to rest inverted on the lawn of a private residence, and the fuselage, tail boom, and wings were substantially damaged. PERSONNEL INFORMATIONThe pilot's flight logbook was recovered from the wreckage. The logbook indicated that the pilot had accrued about 32 hours in Cessna airplanes more than 20 years ago, but then ceased flying until September 2017, when the pilot logged some time in an Aeronca Champ. The pilot's accident report stated that he had accrued a total flight time of 36.1 hours, including 13.6 hours as pilot in command, and 4 hours in the airplane accident make and model in the last 90 days. A search of Federal Aviation Administration (FAA) records did not reveal any pilot or medical certificates for the pilot.

The pilot's wife reported that this was the first time to her knowledge that the pilot had flown the airplane. She reported that he had previously taxied the airpalne, and conducted "crow hopping" exercises in it as well. She defined crow hopping as a maneuver where the pilot would accelerate on the runway and allow the airpalne to become momentarily airborne before touching down and stopping.

For undetermined reasons, the pilot erroneously reported a departure time of 1030, and an accident time of 1045, in his written account of the accident. AIRCRAFT INFORMATIONThe kit-built airplane was registered to the pilot about a year before the accident, but he was not the builder of the airplane. The airplane structure consisted primarily of aluminum tubing covered with fabric skin. The airpalne was equipped with a 50 hp Rotax 503 series engine mounted in an overwing pusher configuration. Pilot-provided information indicated that the airframe had a total time (TT) in service of about 45 hours, and the engine had a TT of about 96 hours. No maintenance records were provided to the investigation. METEOROLOGICAL INFORMATIONThe 1156 automated weather observation at an airport located about 29 miles southeast of the accident site included wind from 160° at 6 knots, visibility 10 miles, few clouds at 6,000 ft, temperature 31°C, dew point 12°C, and an altimeter setting of 30.13 inches of mercury.

Inflight images depicted clear skies, and were consistent with little or no wind. AIRPORT INFORMATIONThe kit-built airplane was registered to the pilot about a year before the accident, but he was not the builder of the airplane. The airplane structure consisted primarily of aluminum tubing covered with fabric skin. The airpalne was equipped with a 50 hp Rotax 503 series engine mounted in an overwing pusher configuration. Pilot-provided information indicated that the airframe had a total time (TT) in service of about 45 hours, and the engine had a TT of about 96 hours. No maintenance records were provided to the investigation. WRECKAGE AND IMPACT INFORMATIONThe accident site was located about 4 miles east-northeast of OR1. Evidence indicated that the airplane struck a tree about 25 yards away from where the airplane came to rest, and that it also struck at least one powerline between the tree and the ground impact point. Ground scars indicated little to no horizontal travel during or after ground impact.

The two FAA inspectors who responded to the accident site on the day of the accident conducted a limited examination of the aircraft, and did not observe any pre-impact damage. Throttle and flight control continuity was unable to be verified. The ailerons, elevator, and rudder all remained securely attached to their respective airfoils and control links. Impact damage precluded determination of the pre-accident integrity of the aircraft structure or its control systems.

The fuel tank was approximately ¾ full, and there was fuel in the bowls of each of the two carburetors. The exhaust manifold was removed from the engine to examine the pistons and cylinders, and no pre-impact damage or abnormalities were observed. ADDITIONAL INFORMATIONA Go-Pro brand video camera was found attached to the exterior of the aircraft. Review of the data on the camera's memory card indicated that the camera recorded the entire accident flight. The camera was mounted low on the outside of the right fuselage, faced forward, and did not capture any aerodynamic surfaces, instruments, controls, or the engine/propeller. Except when the pilot's arm reached out of the cockpit to adjust the camera or something near it, the camera did not capture any of the pilot's anatomy.

The following events (in file elapsed time, format MM:SS) were observed during review of the video file. The airplanet began taxiing on the ramp about 00:15, and stopped on the midfield perpendicular taxiway about 01:20. About 01:48 he resumed taxiing towards the runway, and then the airplane crossed the point-hold line, and entered the airport movement area. About 02:30 the airplane stopped in the movement area between the point hold line and the runway, and remained there for about 30 seconds before entering the runway. The airplane turned left (south) onto the runway, and took about 1 1/2 minutes to taxi to the runway 36 end. The airpalne remained at the left (east) side of the runway for that entire taxi. The aircraft remained on the runway 36 end for about 2 1/2 minutes before it began its takeoff roll. The 14 second takeoff roll was conducted well to the right of the runway centerline. About 2 minutes after takeoff, when the airplane appeared to be level at an altitude of about 500 to 750 ft above ground level, the airplane made a right turn to a heading of east. During the next 3 minutes, the altitude appeared to decrease slowly, and the heading drifted towards the northeast. About 12:30, the airplane turned right, towards the southeast. 20 seconds later, the airplane turned right to a heading of south, and then began maneuvers consistent with an aerodynamic stall. The airplane first banked and turned sharply right, the nose pitched down, and then the airplane banked and turned sharply left, descending rapidly during this sequence. The left and right turns both appeared to result in approximate 180° heading changes. About 13:00, the airplane struck a tree and then impacted the ground. The airplane was descending rapidly in a wings level attitude, and with a forward horizontal velocity component, when it struck the tree. About 14 seconds after the airplane came to rest, significant image vibration, similar to that resulting from engine operation, ceased. The file ended at 17:42; there was no visible activity or camera movement between the time of ground impact and the end of the file.

Contributing factors

  • cause Angle of attack — Not attained/maintained
  • cause Pilot
  • cause Airspeed — Not attained/maintained
  • factor Pilot
  • Contributed to outcome

Conditions

Weather
VMC, wind 160/06kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.