NTSB CAROL · Event
Event CEN22FA031
Registry · N866JA
FAA Aircraft Registry record.
Make / Model
BRITTEN-NORMAN BN-2A
Year of manufacture
1970 · 51 years old at event
Engine
LYCOMING 0-540 SERIES (250 hp)
Seats / Engines
10 seats · 2 engines
Last airworthiness date
19701124
ADS-B equipped
Yes — Mode-S ABE5EA
Registrant of record
MCPHILLIPS FLYING SERVICE INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's exceedance of the airplane's critical angle of attack during final approach, which resulted in an aerodynamic stall and loss of control at an altitude too low to recover.
Factual narrative
HISTORY OF FLIGHTOn November 13, 2021, at 1349 eastern standard time, a Britten Norman BN-2A airplane, N866JA, was substantially damaged when it was involved in an accident near Beaver Island, Michigan. The pilot and three passengers were fatally injured, and one passenger received serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 135 air taxi flight. The ADS-B data showed that the airplane departed Charlevoix Municipal Airport (CVX), Charlevoix, Michigan, at 1332. After departing CVX, the airplane turned north and proceeded directly toward Welke Airport (6Y8), Beaver Island, Michigan. The enroute portion of the flight was conducted about 1,500 ft above mean sea level (msl), and the airplane remained at this altitude until it was about 3 nautical miles (nm) from 6Y8. At this point, the airplane descended and maneuvered toward a straight-in approach to runway 35 at 6Y8. The ADS-B data ended about 0.24 nm south of the accident site. The track data from a handheld GPS that was used in the airplane coincided with the ADS-B data but recorded additional data that ended at the accident site. Figure 1: Overview of the accident flight. ADS-B flight track depicted in blue, GPS flight track depicted in red. Figure 2: Plot of ADS-B and GPS flight track data for the final portion of the accident flight. ADS-B data depicted in blue. GPS data depicted in red. The GPS recorded position, heading, altitude, and ground speed among other data. The airplane’s airspeed was calculated from the GPS groundspeed considering the recorded winds at the Beaver Island Airport (SJX), located about 2 nm southwest of the accident site. When the airplane was 1,200 ft from the runway threshold, the calculated airspeed was 58 knots, and when 600 ft from the threshold the airspeed was 54 knots. The final recorded data point coincided with the wreckage location and the recorded airspeed was 33 knots. Figure 3 depicts the plotted airspeed during the final portion of the accident flight. The chief pilot for the operator witnessed the accident. He stated that he heard the pilot announce that he was at “Sand Bay”, a location that the operator’s pilots use as a reporting point about 5 minutes from the airport. He stated that he left his house, which is adjacent to the airport, to meet the airplane and he could see the airplane was flying very slowly, in a near stall position. He stated that it appeared to be flying nose-up with no power. He realized that the pilot only had a few seconds to lower the nose and add power before the airplane stalled. His first reaction was that the airplane was “wallowing” and no one was flying the airplane. He stated that the airplane did not recover from the nose-high attitude, then stalled and impacted the ground about 100 ft from the runway. Figure 3. Airspeed during the final portion of the flight. PERSONNEL INFORMATIONAccording to the operator’s report, the pilot had accumulated 2,949 hours of total flight experience with 136 hours in the accident airplane make and model. The pilot was hired by the operator on March 20, 2021, and the operator's training records indicated that the pilot completed the company indoctrination, aircraft ground training, emergency training, crew resource management training, special subjects training, flight training, and differences training between March 21 and July 13, 2021. He passed the airman competency/proficiency check in accordance with 14 CFR Parts 135.293, 135.297, and 135.299 on July 21, 2021. The pilot's flight duty summary indicated that his last duty day before the day of the accident was on November 1, 2021, 12 days before the accident. On that day the pilot was on duty for about 9.3 hours, logged 5.5 hours of flight time, and completed 17 landings. WRECKAGE AND IMPACT INFORMATIONThe airplane impacted the ground about 110 ft east of the extended centerline of runway 35, and 320 ft south of the runway threshold. The turf runway was 3,500 ft long and had a displaced threshold just beyond its intersection with paved runway 9/27. Impact signatures indicated that the airplane struck the ground in a left-wing-low, nose-low attitude. The front of the fuselage was crushed upward and aft. Figure 4. Overall view of the airplane wreckage at the accident site. All major components of the airplane were located at the accident scene. Flight control continuity was established from the cockpit controls to each respective control surface except for cuts made by first responders for occupant extraction. Engine control continuity was established from the cockpit to each engine except for cuts made by first responders for occupant extraction. The wing flaps were found in an extended position. Examination of the airframe, engines, and propellers did not reveal any preimpact mechanical malfunction or failures that would have precluded normal operation. ADDITIONAL INFORMATIONThe airplane was a twin-engine, high-wing, strut-braced monoplane with a fixed tricycle landing gear arrangement. It was configured to accommodate 10 people, including the flight crew, with additional baggage capacity behind the passenger seats. The airplane load manifest indicated that the airplane was operating at a weight of 5,903 lbs., and the center of gravity was at 25.3 inches aft of the datum, within the manufacturer’s prescribed weight and center of gravity limits. According to the operator, all passengers and baggage were weighed on a scale before flight. According to the airplane flight manual, for a weight of 6,000 lbs. with flaps down, the stall speed was listed as 42 knots (48 mph). A pilot-rated witness observed the airplane during the final approach to the destination airport and stated that the airplane was flying slowly, with a high pitch attitude, and was “wallowing” as if nobody was flying. The airplane stalled and impacted the ground about 300 ft from the runway. GPS and automatic dependent surveillance-broadcast (ADS-B) data captured the accident flight, but the ADS-B data ended about 0.24 miles before the accident. GPS data showed that the airplane’s speed was at or near the published stall speed for the airplane’s given loading condition. The airplane sustained substantial damage to the fuselage and both wings. Examination of the airplane verified flight and engine control continuity. No preimpact anomalies were found with respect to the airplane, engines, or systems. The pilot allowed the airspeed to decrease during the approach, increased pitch attitude, and exceeded critical angle of attack, which resulted in an aerodynamic stall and spin into terrain. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Airspeed-Not attained/maintained
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Angle of attack-Capability exceeded
- — Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot
Verbatim from NTSB's published report. Source file
NTSB_2021_CEN22FA031.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall, loss of control). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Semantic Scholar 2016 · Article (Interacción)
Trajectory Recovery System: Angle of Attack Guidance for Inflight Loss of Control
This paper describes the design and development of an ecological display to aid pilots in the recovery of an In-Flight Loss of Control event due to a Stall (ILOC-S).
- NTSB Aircraft Accident Reports 2010 · Accident report
Loss of Control on Approach — Colgan Air Flight 3407
Colgan Air 3407 / Continental Connection (Q400) Buffalo NY, February 12, 2009 — 50 fatalities. Definitive investigation of the Colgan 3407 stall-stick-pusher crash on approach to Buffalo.
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- arXiv 2025 · arXiv preprint
Quadratic Programming Approach to Flight Envelope Protection Using Control Barrier Functions
Ensuring the safe operation of aerospace systems within their prescribed flight envelope is a fundamental requirement for modern flight control systems.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.
Browse the full corpus — academia portal ↗