14 Apr 2019: Cessna 172 N — 2BAPilot NYC Flight School and Aircraft Rental

14 Apr 2019: Cessna 172 N (N5296H) — 2BAPilot NYC Flight School and Aircraft Rental

No fatalities • New York, NY, United States

Probable cause

The pilot's decision to initiate a flight into low instrument flight rules conditions, which resulted in six missed approaches at two airports and a total loss of engine power due to fuel exhaustion. Contributing to the accident was the external pressure the pilot felt to complete the accident flight despite the poor weather conditions.

— NTSB Determination

Accident narrative

On April 14, 2019, about 2215 eastern daylight time, a Cessna 172N, N5296H, was substantially damaged when it impacted a building and powerlines during a diversion to John F. Kennedy International Airport (JFK), New York, New York. The private pilot and two passengers sustained minor injuries. The airplane was registered to N5296H LLC. and operated by 2BAPilot NYC Flight School and Aircraft Rental under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight. Night instrument meteorological conditions prevailed, and an instrument flight rules flight plan was filed for the flight that originated from Niagara Falls International Airport (IAG), Niagara Falls, New York about 1710 and was destined for Republic Airport (FRG), Farmingdale, New York. The pilot reported that on the morning of the accident, he and his passengers arrived at FRG airport about 0630 and departed for IAG, arriving about 1100. They spent the day in the area and departed to return with a direct route to FRG; while enroute, the pilot reported that his planned route was changed by air traffic control which increased the enroute time by about 40-50 minutes longer than he had expected. Once arriving into the FRG area, he attempted a precision instrument landing system (ILS) approach to runway 14 which resulted in a missed approach. He attempted the ILS approach again, and on this attempt, "saw some lights," but was unable to see the runway and performed another missed approach. The pilot attempted the FRG ILS runway 14 approach for a third time, and during the approach he noticed that there was "something wrong with the heading indicator." He realized his course was "zigzagging," so he began to have a passenger tell him what the track heading was displaying on an electronic flight bag application; he subsequently decided a "bigger airport will be better" so he diverted to JFK, via radar vectors from air traffic control. The pilot reported that he attempted three ILS approaches to runway 22L at JFK. The first two resulted in missed approaches, and on the third attempt, the pilot reported that the "fuel went out" and the "engine totally stopped." During the power out descent, he flew the "best glide speed" and about 100 ft above ground, he saw streetlights and made a left turn towards a road. While in the turn the airplane impacted the roof of a building and powerlines. The airplane came to rest entangled in the power lines suspended just a few feet above the ground; the pilot and passengers were able to exit from the main cabin doors onto the street below. The pilot reported that he utilized a timing method for his fuel consumption, because he noticed that after about one hour of flying time enroute, both fuel gauges were stuck indicating full. He believed he had about 5 hours and 20 minutes of fuel onboard at takeoff, which was a full 42 gallons. The pilot reported that he expected the accident flight to take about 3 hours and 30 minutes; however, the total flight time was about 5 hours and 5 minutes. Review of an FAA summary of air traffic control and pilot communications revealed that controllers provided the pilot with several observation weather reports and pilot reports (PIREPs) during his approaches at FRG and JFK. They also requested and received updates from the pilot regarding his low fuel state during the approaches. The record revealed that the pilot did not declare an emergency throughout the flight; however, during the diversion to JFK, air traffic control internally designated the flight as an emergency and had alerted emergency equipment prior to the airplane's loss of engine power. According to a Federal Aviation Administration (FAA) inspector who examined the airplane at the accident site, the fuselage, wings, and empennage sustained substantial damage. There was no odor of fuel at the accident site, nor was fuel observed in the wing tanks. A subsequent examination of the engine found no pre-impact mechanical malfunctions or failures that would have precluded normal operation. Additional examination of the vacuum system found that the pump remained intact, the drive coupling operated normally, there were no blockages observed in the vacuum air hoses, and the pump's wear indicator was within normal operational limits. According to FAA airmen records, the pilot held a commercial pilot certificate with ratings for airplane single and multi-engine land, and instrument airplane. He held a first-class medical certificate issued in January 2018. The pilot reported that he had logged about 80 hours of simulated instrument flight time, of which one hour was in actual instrument conditions and that flight was with a flight instructor. He reported that the accident flight was his first flight in actual instrument conditions as the pilot in command. According to FAA airworthiness records, the 4-seat high wing airplane was powered by a Lycoming O-320-H2AD 160-horsepower engine. The most recent annual inspection was completed in January 2019. According to an NTSB weather study, about the time of departure from IAG and throughout the cross-country flight, IFR conditions were observed at the destination airport and the filed alternate airport (LaGuardia Airport (LGA), New York, New York). The weather conditions reported at FRG and JFK during the pilot's approaches included low visibility and cloud ceilings. At 2153 the weather conditions reported at FRG were, visibility 1/4-mile, fog, vertical visibility 200 ft above ground, wind 200° at 8 knots, temperature 14°C, dew point 14°C, and barometric pressure of 29.65 inches of mercury. One-hour prior at FRG, the visibility and cloud ceiling were the reported as the same (visibility 1/4-mile, fog, vertical visibility 200 ft). At 2212 the weather conditions at JFK were, visibility 1/8-mile, fog, vertical visibility 200 ft above ground, wind 180° at 15 knots, temperature 13°C, dew point 13°C, and barometric pressure of 29.64 inches of mercury. About the time of the accident, FRG, JFK, LGA, and several other New York area airports were observing low IFR conditions. Figure 1 depicts the surrounding weather observation reports at the time of the accident.

Figure 1: Weather Observations at the Time of the Accident in the New York Area

Forecast weather products issued prior to the departure from IAG, including AIRMETs and Terminal Aerodrome Forecast (TAFs), called for low IFR conditions at the accident airport and surrounding airports about the time of the pilot's estimated time of arrival. According to Leidos Flight Service, there was no record that the pilot requested a weather briefing for the accident flight. The pilot reported in a written statement that, "I found that FRG will be bad weather but one of my friend need to go Korea next day. I decide to try to come back, and alternate LGA, because I could land [at] big airport." The FAA Pilot's Handbook of Aeronautical Knowledge provided a variety of tools regarding aeronautical decision making. One such item was the "PAVE" checklist. The FAA PHAK stated in part: The PAVE Checklist Another way to mitigate risk is to perceive hazards. By incorporating the PAVE checklist into preflight planning, the pilot divides the risks of flight into four categories: Pilotin-command (PIC), Aircraft, enVironment, and External pressures (PAVE) which form part of a pilot's decision-making process. E = External Pressures External pressures are influences external to the flight that create a sense of pressure to complete a flight—often at the expense of safety. Factors that can be external pressures include the following: Someone waiting at the airport for the flight's arrival A passenger the pilot does not want to disappoint The desire to demonstrate pilot qualifications The desire to impress someone (Probably the two most dangerous words in aviation are "Watch this!") The desire to satisfy a specific personal goal ("get-there-itis") The pilot's general goal-completion orientation

Contributing factors

  • cause Pilot
  • cause Decision related to condition
  • cause Decision related to condition
  • cause Decision related to condition
  • cause Fluid management
  • Fluid level
  • factor Pilot

Conditions

Weather
IMC, wind 180/15kt

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.