WPR21FA045 · Cessna 177 B
Cessna 177 B · Accident: loss of control in flight on approach
From Bellingham International Airport (BLI) to King County International Airport - Boeing Field (BFI)
Event
- NTSB case
- WPR21FA045
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 2 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 177 B
- Aircraft type
- Cessna 177
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N34633
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bellingham International Airport (BLI), Bellingham, WATo King County International Airport - Boeing Field (BFI), Seattle, WA
- Aircraft age
- About 47 years (built 1973)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
About 16 minutes after takeoff, at 6,500 ft above mean sea level , the airplane’s groundspeed decreased and the airplane started to descend. Shortly thereafter, the flight instructor reported to air traffic control that they were declaring an emergency because they were at full power and rpm setting, and about to lose the engine. They were also unable to maintain altitude. The airplane continued southeast for about 2 miles when it made a left turn east and then back to the southeast. The flight instructor reported they had a little power but were still descending. He further stated that the engine would not stay on for very long and they were at idle power. The controller asked if he had carburetor heat on and he replied “affirmative.”
Shortly thereafter, the flight instructor reported that they did not have engine power and they were going directly to nearby Whidbey Air Park, Langley, Washington. The airplane crossed and flew over a highway before turning north to the airport. Shortly thereafter, the flight instructor stated they were diverting off-airport and the airplane track turned right away from the airport. However, about 15 seconds later he reported the airport insight and the airplane’s track changed back toward the airport. There was no further communication from the accident airplane. The last radar point was over the runway at an altitude of about 300 ft.
A witness reported who was at the airport observed the accident airplane about pattern altitude passing from west to east. The accident airplane continued slightly east of the airport before it made a left turn to a northwest heading. It appeared as if the airplane was “porpoising,” continuously nosing up and down. He noted that the propeller was not turning and there were no audible engine sounds. As the airplane passed over the runway the left wing dropped, and the airplane spun out of sight behind the trees and hangars. Shortly thereafter, the witness heard the impact. The airplane came to rest about 153 ft west of the runway surface against trees that were about 65 ft tall. The witness account and the condition of the wreckage were indicative of the flight instructor’s failure to maintain airspeed, which resulted in an aerodynamic stall and subsequent spin. A postaccident airframe and engine examination did not reveal any anomalies that would have precluded normal operations. The airplane’s engine monitoring system revealed the carburetor temperature had been steadily decreasing from 31°F during the accident flight. When the carburetor temperature reached 17°F there was an abrupt decrease in fuel flow and a corresponding reduction in exhaust gas temperatures. For the remainder of the flight, the exhaust and cylinder head temperatures slowly decreased, and the carburetor temperature slowly increased. The fuel flow spiked several times but immediately decreased.
The nearest weather reporting station reported the temperature as 6°C and dewpoint, 2°C. When plotted on the carburetor ice chart, this temperature dewpoint spread is consistent with serious icing at cruise power. Therefore, it is likely carburetor ice was building during the accident flight and it eventually starved the engine of fuel.
Probable cause
The flight instructor’s failure to maintain airspeed, which resulted in an aerodynamic stall and subsequent loss of control while attempting to conduct an emergency landing. Contributing to the accident was a total loss of engine power as a result of carburetor icing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR21FA045
- Event ID
- 20201111102268
- Case number
- WPR21FA045
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 4c39e4778d23f4ebeafa1f3c6a25ff025288175c27f3a7f07e23fa7f94227a40; retrieved 2026-09-15T07:22:18.289Z.