16 Sep 2010: PIPER PA-18 — RODGERS JUSTIN C

16 Sep 2010: PIPER PA-18 (N9699P) — RODGERS JUSTIN C

No fatalities • Dillingham, AK, United States

Probable cause

Both pilots’ failure to see and avoid each other during initial climb, resulting in a midair collision. Contributing to the accident was the pilot of N9699P’s inability to use his airplane's radio for air traffic advisories.

— NTSB Determination

Accident narrative

On September 15, 2010, about 1840 Alaska daylight time, a float-equipped Piper PA-18 airplane, N9699P, sustained substantial damage during takeoff-initial climb from a floatplane lake, when it collided midair with another float-equipped Piper PA-18 airplane, N2FD, which also sustained substantial damage. The accident occurred about 3 miles west of Dillingham, Alaska. The airplanes were being operated by the pilots as visual flight rules (VFR) personal local flights under the provisions of 14 Code of Federal Regulation Part 91. The solo commercial pilot of N9699P received serious injuries, and the solo private pilot of N2FD received minor injuries. Visual meteorological conditions prevailed, and no flight plans were filed.

During a telephone conversation with the National Transportation Safety Board (NTSB) investigator-in-charge (IIC) on September 24, the pilot of N9699P said he and the pilot of N2FD were friends, and that they were both departing for the same destination. He said during a preflight inspection of his airplane he found the master switch on, and the battery was dead. He said he hand-propped the airplane, and taxied on the lake to warm up the engine. The pilot said when he applied power for takeoff, the other airplane was to his left and behind him. He said he was not able to use the airplane's radio due to the dead battery, and the alternator had not kicked in to start charging the battery. He said his intent was to climb straight out to the south from the lake, and then turn east toward their destination. He said as the airplane climbed toward the edge of the lake, he saw something that flashed by, and he heard a loud noise. He said he lost control of the airplane, and it impacted the ground next to the floatplane lake. He said the airplane received substantial damage to both wings and the fuselage.

During a telephone conversation with the NTSB IIC on October 1, the pilot of the other accident airplane, N2FD, said that he had made arrangements with the pilot of N9699P to meet at another location after departing their mutual home floatplane lake. He said he had started his airplane, and was taxiing on the lake. He contacted a nearby FAA flight service station via the airplane's radio, who advised of helicopter traffic in the area. He said he did not hear N9699P on the radio, and that the last time he saw N9699P, it was on the lake to his right, and he believed taxiing to warm up its engine. He said he applied takeoff power, believing that he was the first to leave, and was not aware that N9699P was also taking off. He said he heard a loud bang, and thought something had broken on his airplane causing a loss of control and the crash. The pilot said he did not know he had collided with another airplane until he exited the wreckage on the ground. He said the airplane received substantial damage to both wings and the fuselage.

On September 30, the IIC contacted a witness to the accident via telephone. The witness said he was in his residence adjacent to the floatplane lake, and heard two airplanes power up, one right after the other. He said it was unusual for two airplanes to takeoff at the same time, and he looked outside to watch. The witness said he was familiar with both airplanes and pilots, and that he did not know which airplane powered up first. He said both airplanes started to takeoff from different areas on the same side of the lake, and they were headed in the same direction. He said both airplanes lifted off the water and started to climb. He said N9699P was to the right of N2FD, and that N9699P appeared to be in a slight left bank. He said about 50-70 feet above the water, N9699P appeared to come up underneath N2FD's right wing. The witness said the airplanes collided, and tumbled to the shore of the lake.

Contributing factors

  • cause Pilot
  • cause Pilot of other aircraft
  • factor Inoperative
  • cause Pilot
  • cause Pilot of other aircraft
  • factor Inoperative

Conditions

Weather
VMC, wind 180/08kt, vis 30sm

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.