NTSB News Talk – Aviation Accidents, Safety Investigations & Pilot Lessons

In this episode of NTSB News Talk, hosts Max Trescott and Rob Mark welcome Michael Graham, a current member of the National Transportation Safety Board (NTSB), for a deep discussion on the agency’s work and the broader state of aviation safetyGraham begins by clarifying the role of NTSB board members, often misunderstood as investigators. While trained in accident investigation, board members function more like the “Supreme Court of Transportation Safety,” deliberating on reports and voting on recommendations that flow from investigative teams. They also serve as media spokespeople at accident sites, coordinate with local authorities, and meet with victims’ families.A major portion of the conversation focuses on advocacy—convincing regulators, manufacturers, operators, and associations to implement safety recommendations. Graham acknowledges that implementation can take years or even decades, citing the long struggle to mandate Positive Train Control in the rail sector. Despite delays, the board persists in pushing for life-saving changes.The discussion then shifts to Safety Management Systems (SMS). Graham describes his advocacy for SMS across Part 135 operators, manufacturers, and repair stations, and highlights FAA Advisory Circular AC 120-92D, which now provides scalable SMS guidance for small operators and even single-pilot GA. This, he says, is a breakthrough that makes SMS practical outside of large organizations.From his Navy background, Graham stresses the role of safety culture: open communication, willingness to accept critique, and rigorous debriefs after every mission. He encourages GA pilots to adapt these practices by critiquing their own flights, flying with peers who can offer feedback, and leveraging available flight data tools. Pilots, he argues, must move past ego and embrace constant improvement.Graham also highlights spatial disorientation as a persistent and deadly problem. While only a fraction of GA accidents involve it, more than 90% are fatal. He recalls accidents such as the 2019 Amazon Air crash near Houston, underscoring the importance of proficiency in instrument flying. Pilots, he warns, must remain both current and truly proficient to avoid disaster.The conversation touches on technology as an engineering control for safety. Graham sees promise in ADS-B In for situational awareness, particularly in congested or uncontrolled airspace, and advocates for broader adoption. He also points to angle of attack indicators as an underused but powerful tool for GA pilots to understand aircraft performance margins.Additional topics include lessons from the NTSB’s General Aviation Dashboard, frustrations with slow NextGen implementation and ATC staffing, and the destruction of the TWA 800 reconstruction once displayed at the NTSB Training Center. Graham also describes his path to the board, from Textron safety leadership to a lengthy nomination and confirmation process, and the challenges of balancing safety priorities with limited agency staffing.Throughout, Graham emphasizes that aviation safety is never static. A safe state is not permanent; it requires constant vigilance, adaptation, and recognition of new risks. For pilots and organizations alike, the lesson is clear: success comes from continuous critique, data-driven decision-making, and openness to feedback.This wide-ranging interview provides both a candid look inside the NTSB and actionable lessons for GA pilots, safety professionals, and anyone passionate about preventing accidents.

Episode 12 of NTSB News Talk with hosts Max Trescott and Rob Mark delivers a comprehensive discussion of recent accidents, preliminary findings, and final NTSB reports, highlighting recurring safety themes for GA pilots.The episode begins with the White House nomination of American Airlines captain John DeLouv to the NTSB board, and an invitation for listeners to suggest questions for an upcoming interview with a board member.The first accident examined is a Lancair Super ES crash near San Jose on September 12, 2025. ADS-B data showed unusual behavior, with a temporary TIS-B hex code indicating the aircraft may have suffered an electrical failure. The pilot completed odd turns, steep descents, and eventually lost control, reminiscent of a prior electrical-failure accident on the East Coast. The takeaway: system failures can snowball, and pilots should land at the first safe opportunity.Next, the hosts review a Bonanza BE-35 accident in Denver after multiple touch-and-goes. The ADS-B track suggested reduced altitude, slower speeds, and eventually a likely engine failure. The pilot attempted a turnback but fatally crashed. Max and Rob emphasize the priority of aviate–navigate–communicate, reminding pilots that talking to ATC should never outweigh flying the airplane.Two Cirrus SR22 accidents highlight starkly different outcomes. In Michigan, a Gen 6 SR22T ditched in Lake Michigan after an oil pressure failure. The pilot deployed CAPS, and thanks to a nearby Malibu and quick Coast Guard response, all aboard were rescued uninjured. In contrast, an SR22 in Franklin, North Carolina, crashed fatally during a go-around, illustrating how seldom-practiced procedures lead to errors with trim, flaps, and rudder control. The hosts urge pilots to rehearse go-arounds regularly.The preliminary reports shift focus to Shelter Cove, California, where a student pilot illegally carrying a passenger crashed into fog, killing himself and injuring the passenger. The case illustrates hazardous attitudes like anti-authority and the risks of taking unqualified passengers. Another case, a Cessna 340 in Missouri, involved a fatal stall-spin during pattern entry, with eyewitnesses describing a wing drop consistent with low-speed loss of control.Among final reports, the hosts cover a widely discussed PA-28 accident in Kentucky in which a young CFI posted on social media mid-flight before pressing into nighttime thunderstorms. Misunderstanding NEXRAD latency and underestimating storm hazards led to an in-flight breakup. In another Bonanza case in Georgia, a pilot attempted a steep turnback shortly after takeoff with the gear down, stalled, and crashed into a residential area despite a functioning engine. The accident raises questions about distraction, possible door issues, and the dangers of early turnbacks.The show closes with the Citation 550 crash in Murrieta, California, in July 2023. Two relatively low-time pilots flew two approaches into deteriorating fog. On the second, they descended below minimums and struck terrain short of the runway. Factors included fatigue at a circadian low, unstable approach speeds, dark-hole illusions, and potential pressure to get home. Max recalls his earlier Aviation News Talk analysis, suggesting the pilots may have mistaken a nearby white-roofed building for runway markings. The NTSB ruled controlled flight into terrain.Episode 12 underscores repeating patterns: hazardous attitudes, poor weather decisions, under-practiced maneuvers, and fatigue all contribute to accidents. By analyzing both new and final reports, Max and Rob provide actionable reminders for pilots to respect limitations, practice essential maneuvers, and make conservative choices when safety is at stake.

Max talks with Rob Mark about the latest NTSB cases and safety lessons for pilots. They begin with new details on the B-52 near miss at Minot, North Dakota, where the bomber nearly collided with both a regional jet and a Piper Archer. The tower controller, working alone without radar support, became overwhelmed and failed to advise the B-52 crew of conflicting traffic. At one point, he even issued incorrect altitude and heading clearances. Though everyone avoided contact, the case illustrates that controllers can—and do—make mistakes, making pilot vigilance essential.Attention then turns to a fatal midair collision in Fort Morgan, Colorado, where a Cessna 172 on a straight-in approach collided with an Extra 300 turning base just after an aerobatic contest. Because of their high- and low-wing configurations, each aircraft was hidden in the other’s blind spot. The accident underscores the importance of CTAF communication, traffic scanning, and using a second radio to monitor the local frequency even while on IFR clearances.Rob next reports on a Cessna 172 from San Jose’s Reid-Hillview Airport whose pilot declared jammed flight controls. Another pilot attempted to assist in the air, but the aircraft ultimately crashed. The case recalls earlier accidents where loose objects, like portable GPS antennas, jammed control linkages.The episode also examines student pilot tragedies. In Lock Haven, Pennsylvania, a young student turned crosswind too soon at low altitude and struck trees. In New Jersey, a 61-year-old student in a Cirrus SR20 succumbed to somatogravic illusion, leveling off at night and descending into terrain after takeoff. Both highlight the risks of solo flight without CFI oversight and the dangers of night solos.Further cases include a Cessna 152 overrun at night in Kansas with a pilot who fled the scene, a T-6 Texan stall/spin at Oshkosh caused by low-speed maneuvering, and a Cessna 206 crash in Alaska where water-contaminated fuel led to an engine failure.Throughout the discussion, Max and Rob emphasize recurring themes: respect stall speeds and G-loading, always sump fuel, avoid complacency with ATC instructions, and never assume other pilots are on frequency. Their message is clear—aviation safety depends on every pilot maintaining situational awareness, discipline, and respect for physics.

In Episode 10 of NTSB News Talk, aviation safety experts Max Trescott and Rob Mark examine recent accident reports that reinforce why loss of control in flight continues to be the number one cause of fatalities in general aviation. Drawing from official NTSB accident reports and preliminary findings, they analyze crashes involving a TBM turboprop in Montana, a Beechcraft King Air in Arizona, and other cases where night flying illusions and equipment failures played a decisive role.TBM Crash in Kalispell, MontanaRob begins with an August accident in Kalispell, Montana, where a TBM turboprop attempted to land at the city airport. Witnesses said the aircraft touched down near the approach end of the runway before veering into parked planes, sparking a fire. Incredibly, all four occupants survived with only minor injuries. Though details are still sparse, the incident highlights how quickly loss of control can occur even in a high-performance single-engine turboprop.Max and Rob stress that while the TBM is an advanced and capable aircraft, any landing can go wrong if the pilot mismanages energy or fails to stabilize the approach. This accident serves as a reminder that precision, discipline, and preparation remain critical during the landing phase, when the margin for error is smallest.King Air 300 Crash in Chinle, ArizonaThe hosts then turn to a tragic August 5th accident involving a Beechcraft King Air 300 on the Navajo Nation in eastern Arizona. The aircraft was inbound on a medical transport flight, but before picking up its patient it crashed near the single runway at Chinle Municipal Airport. All four aboard—two pilots and two healthcare providers—were killed.Conditions that day created a perfect storm: a density altitude of over 8,400 feet combined with gusty crosswinds approaching 28 knots, nearly 90 degrees to the runway. The demonstrated crosswind limit for the King Air 300 is 20 knots, but as Rob explains, that number is not a hard limitation—it simply reflects the strongest crosswind tested during certification. What really matters is pilot proficiency.The Chinle crash underscores the dangers of trying to land in challenging conditions when performance margins are already compromised by high elevation and high temperature. For many pilots, especially those not flying crosswind landings regularly, the combination can quickly exceed skill level and lead to loss of control.Cessna Conquest II Crash in OhioRob next covers a preliminary report on a Cessna Conquest II that departed Youngstown, Ohio, en route to Bozeman, Montana. Security video showed the aircraft lifting off after a normal ground roll, but instead of climbing, it leveled off at just 100 feet and maintained that altitude until impacting trees. Both engines were reportedly running, making the lack of climb especially puzzling.Witnesses described unusual engine sounds, but Max and Rob note that eyewitness accounts are often unreliable. The bigger mystery is why the pilot failed to climb, despite having ample power available. Possible scenarios include distraction, incapacitation, or improper handling of the aircraft. As Max points out, 80 percent of accidents are linked to human error, and this crash may ultimately fall into that category.Night Illusions and the Needles, California AccidentMax then shares insights into a Piper PA-28 crash in Needles, California, where two low-time pilots were building hours for airline transport certification. After a go-around at night, the aircraft crashed almost immediately. The conditions—dark desert terrain with no horizon—were ideal for somatogravic illusion, a common cause of accidents at night.Somatogravic illusion occurs when acceleration tricks the body into feeling like it is pitching up, leading pilots to push forward on the controls when they should be climbing. With little visual reference and limited experience, the pilots in this case likely succumbed to the illusion. Max emphasizes that pilots flying in dark-night conditions must always cross-check instruments, especially the vertical speed indicator, to confirm a positive rate of climb.Final Reports: Mooney in Maryland and King Air in HawaiiThe episode also examines two final NTSB reports. The first involved a Mooney that struck power lines near Gaithersburg, Maryland, while flying an approach in dark night IMC. Photos of the aircraft wedged into a transmission tower made national headlines. The investigation revealed the pilot was unfamiliar with his IFR-certified GPS and often relied on a handheld unit instead. Poor avionics knowledge combined with descent below minimums led to the crash.The second report focused on a Hawaii medical transport King Air C90 that crashed into the ocean at night after its attitude indicator failed. Cockpit video captured the pilot listening to music and chatting with crew before the failure, and later struggling to control the aircraft without reliable instruments. The NTSB cited inadequate training and a history of poor checkride performance as contributing factors. The accident reinforced the critical need for proficiency in hand-flying and backup instrument skills.Key Lessons for PilotsThroughout the discussion, Max and Rob emphasize several recurring themes:Loss of control remains aviation’s deadliest risk. Even experienced pilots can miss upset cues or fall victim to illusions.Avionics knowledge is essential. Pilots must know their GPS and autopilot systems thoroughly to avoid confusion in high-stress situations.Simulator training pays off. Practicing hand-flying, instrument failures, and upset recovery in a safe environment builds resilience.Dark-night conditions are uniquely hazardous. Without lights or a horizon, illusions can overwhelm even competent pilots.Altitude and proficiency are survival tools. Whether flying a TBM, King Air, or a light single, the best defense is disciplined flying and constant preparation.Episode 10 of NTSB News Talk demonstrates that while technology and aircraft performance continue to advance, pilot proficiency and decision-making remain the decisive factors in aviation safety. From Montana to Arizona, Ohio to Hawaii, the NTSB’s accident reports show that staying sharp, staying current, and understanding the human factors behind loss of control can save lives.Please check out these other podcasts in the Aviation News Talk Network:Aviation News TalkRotary Wing Show Podcast UAV News Talk Podcast 

On this episode of NTSB News Talk, Max Trescott covers the third and final day of the NTSB’s investigative hearing into the January 2024 midair collision near Washington’s Reagan National Airport between a PSA Airlines CRJ-700 and a U.S. Army UH-60L Black Hawk. Day 3 featured Panel 4: Collision Avoidance Technology and Panel 5: Safety Data and Safety Management Systems.The hearing opened with spatial disorientation testimony and interviews with Army pilots about Route 4 altitude protections they incorrectly believed would keep them clear of Runway 33 arrivals. NASA’s Dr. Stephen Casner explained that cockpit traffic displays can help pilots spot targets up to eight times faster than by visual scan alone.Experts detailed ADS-B system complexities — including the two incompatible broadcast frequencies (UAT and 1090ES) — and reviewed the limits of pre-ADS-B collision avoidance technology. The UH-60L Black Hawk lacks integrated traffic displays, relying instead on iPads with Stratus receivers, which Army policy prohibits the flying pilot from using. Portable ADS-B In devices provide only partial traffic pictures unless paired with ADS-B Out, limiting situational awareness.Discussions turned to TCAS: its nuisance alert problem, differences for helicopter operations, and why the CRJ-700 lacks a certified ADS-B In solution. The NTSB Chairwoman confronted the FAA over its 17-year refusal to mandate ADS-B In, despite repeated post-collision recommendations. The Army is now procuring 1,685 Stratus/iPad sets for priority units, but operational use will still be limited at low level.FAA data revealed 366 TCAS resolution advisories within 10 nm of DCA from 2023–2025. Testimony noted that crews involved in RAs are typically not notified unless a deviation occurs. Panelists debated safety culture, just culture, and leadership removals at DCA Tower after the accident. A controller supervisor described the pre-accident culture as “robust,” but post-accident changes removed key institutional knowledge.The hearing also exposed gaps in PSA pilot special-qualification training for DCA — including no information on helicopter routes or operations — and examined simulator results showing that circling to Runway 33 can double or triple pilot workload compared to a straight-in to Runway 1.Closing testimony on future ACAS XR technology indicated it could have alerted the Black Hawk crew 73 seconds before impact, with potential nationwide deployment by 2027. Max weaves these details into a narrative showing how technological shortfalls, flawed assumptions, procedural gaps, and cultural challenges all converged in this tragic midair — and what reforms could prevent a repeat.NTSB Docket on Reagan National midair collisionCheck out our other Aviation News Talk Network podcasts:UAV News Talk Podcast Rotary Wing Show PodcastAviation News Talk

Max Trescott plays audio clips from Day 2 of the NTSB investigative hearing on the midair collision near Washington’s Reagan National Airport between a PSA Airlines CRJ-700 and a U.S. Army UH-60L Black Hawk. This day focused exclusively on Panel 3: Training, Guidance, and Procedures Applicable to DCA Air Traffic Control, revealing systemic issues that shaped the events leading to the accident.A major theme was visual separation. Testimony explored the difference between pilot-applied and tower-applied visual separation in Class B airspace and the operational norm at DCA where helicopter pilots almost reflexively request pilot-applied visual separation. Experts explained how the unique combination of restricted airspace, helicopter routes, and runway configurations makes visual separation “paramount” for traffic flow, though it shifts collision avoidance responsibility to pilots. A U.S. Army pilot described the difficulty of spotting Runway 33 arrivals at low altitude, highlighting how these challenges contributed to the accident sequence.Staffing emerged as a critical factor. The DCA tower had 19 fully operational controllers to cover 16 shifts a day, forcing position combinations such as merging tower and helicopter frequencies. Witnesses described high workload and a culture summed up by the phrase “just make it work,” raising questions about whether safety margins were being eroded. A management-level request to reduce arrival rates from 32 to 28 per hour due to safety concerns was denied, reportedly over political timing related to FAA reauthorization.The hearing also examined miles-in-trail spacing, revealing inconsistent agreements between Potomac TRACON and DCA Tower and noting that arrivals were being fed at less than four miles apart before the accident. Conflict alert systems were scrutinized, with testimony that up to 50% of alerts are “nuisance alerts,” that could lead to controller desensitization. The Black Hawk’s lack of ADS-B Out was discussed, though radar coverage mitigated its effect on conflict alerting in this case.Additional revelations included confusion over helicopter route altitudes, the tower’s downgrade from Level 10 to Level 9 (which resulted in new controllers being paid at a lower level than existing controllers), and an external compliance audit that found 33 areas of non-compliance—so severe the audit was halted and converted into an internal corrective action. The episode also covers the failure to conduct alcohol testing at all of controllers after the accident, contrary to the DOT’s two-hour requirement.Max weaves over an hour of testimony into a narrative that exposes the intersection of human factors, training gaps, and systemic pressures inside one of the nation’s most complex airspace environments. The episode underscores how a combination of cultural norms, operational constraints, and safety oversight gaps set the stage for this tragic collision—and what must change to prevent future accidents.NTSB Docket on Reagan National midair collisionCheck out our other Aviation News Talk Network podcasts:UAV News Talk Podcast Rotary Wing Show PodcastAviation News Talk

Jennifer Homendy, the NTSB Chair, dives into her frustrations with the FAA’s response to the tragic midair collision near Reagan National Airport. Topics like serious inaccuracies in helicopter altimeters highlight systemic safety flaws. Detailed analyses of communication before the crash reveal critical misunderstandings between air traffic control and pilots. The conversation emphasizes the need for improved aviation safety protocols and better documentation practices to prevent future tragedies and protect lives.

Max and Rob bring listeners a packed episode of aviation safety lessons anchored by the NTSB. They begin with the Board’s announcement of a three-day investigative hearing into the Reagan National midair between a regional jet and a U.S. Army helicopter. Rob dives into a dramatic close call in North Dakota, where a Delta Regional Jet on final narrowly avoided a B-52 bomber crossing its flight path near Minot. The incident exposes communication gaps, contract tower limitations, and the critical need for radar and coordination between military and civilian traffic.In Mexico City, a Delta A320 rejected a high-speed takeoff to avoid an AeroMexico E-190 landing over the top of it on the same runway. The event raises red flags about ATC language use, as Spanish transmissions prevented the Delta crew from maintaining situational awareness. Max explores the Hollister RV-8/Cirrus collision, highlighting how a relocated runway threshold and lack of radio calls can set the stage for disaster. A video of the midair was posted on Facebook. AOPA's Sweepstakes Aviat A-1C-200 Husky was damaged in a landing incident, in which the pilot's left foot was misplaced an not on the rudder pedal.A Murphy Aircraft Manufacturing Limited Moose airplane, N250MK, was destroyed when it was involved in a takeoff accident near Montrose, CO. According to the Preliminary NTSB report, two pilots on board were killed. The Falcon 10 runway overrun in Panama City offers a textbook example of checklist discipline when thrust reversers failed due to switches left in the wrong position, turning deceleration into forward thrust. The AOPA Sweepstakes Husky mishap adds another cautionary tale about cockpit discipline and distractions.The episode’s most personal moment comes when Rob shares his experience flying rusty in a G1000-equipped Cessna 182. Fatigue, cockpit visibility issues, haze, and a failed trim system combined to erode his performance and highlight how ego can mask risk. Max underscores the I’M SAFE checklist—illness, medications, stress, alcohol, fatigue, emotion—and how self-awareness can prevent tragedies. Together, they emphasize that open discussion and honest reflection are vital to improving safety and preventing accidents.Check out our other Aviation News Talk Network podcasts:UAV News Talk Podcast Rotary Wing Show PodcastAviation News Talk

Max Trescott and Rob Mark return for episode five of NTSB News Talk with a full slate of recent accidents and preliminary reports that highlight critical lessons in decision-making, mechanical failure, and situational awareness.They start with the tragic crash of a Cirrus SR22 in North Carolina that killed a family of four. The aircraft had experienced electrical issues early in the flight, and despite indications of ongoing problems, the pilot chose to continue to the destination rather than land. Max emphasizes how what may seem like a minor issue—such as an alternator failure—can escalate, especially if the pilot doesn’t fully understand the systems or how cascading failures can emerge.Next, they examine a mid-air collision in Steinbach, Manitoba between two Cessna training aircraft. Despite clear weather and an active pattern, both pilots were killed. Max reminds listeners that most mid-airs happen close to airports, often on final. Rob adds that see-and-avoid doesn’t always work, especially with sun glare or poor traffic sequencing.They then move to a bizarre and poorly documented case of a Cessna T240 that departed Ramona, California and flew 400 miles offshore before descending into the Pacific. With no radio contact and the aircraft failing to respond to repeated ATC calls, the case raises the possibility of a medical event or incapacitation. The plane was never recovered.A medical charter King Air crash in London, UK, is briefly discussed. The aircraft appeared to roll left and crash immediately after takeoff. Rob stresses the importance of immediate rudder input and pitch control following engine failure in twins.A major focus of the episode is the preliminary report on Air India Flight 171, a Boeing 787 that lost both engines seconds after rotation. Both fuel cutoff switches moved from RUN to CUTOFF, then briefly back. One pilot is heard asking, “Why did you cut the fuel?” The other responds, “I didn’t do anything.” Rob and Max explore the implications of this odd event, especially in light of a 2018 FAA bulletin about fuel control switch locking mechanisms. Despite the non-mandatory nature of the bulletin, it directly referenced the potential for disengagement of the locking feature. Rob explains how the switches require a deliberate lift-and-pull action to move into CUTOFF, making accidental movement unlikely. Suicide and sabotage are also deemed improbable.The discussion turns back to U.S. reports, including a crash in Montana where a Cessna 172 flew low and hit unmarked power lines. Max reiterates how hard it is to see wires until it's too late. Rob reflects on his own youthful low-level flying and how little awareness he had of such hazards at the time.They then discuss a helicopter crash in Alaska. A Robinson R66 pilot operating in flat, snow-covered terrain under a 500-foot overcast likely experienced whiteout conditions and lost situational awareness. Max explains how disorientation is common in visually featureless environments—recounting his own night flight in hazy conditions where city lights and stars blurred together.They also dissect a De Havilland Twin Otter crash in Tennessee during a skydiving flight. A left engine power loss forced a turnback attempt. The aircraft crashed into trees short of the runway, severely damaging the left wing and engine. Six people were seriously injured, though none killed. Rob questions the decision to add flaps during the emergency and notes the pilot’s inability to confirm if he secured the failed engine.Finally, the hosts cover the NTSB final report of a 2023 Cessna 172 crash near San Rafael, CA. The pilot failed to apply carb heat during descent at night and suffered an engine failure. The aircraft struck a power line and terrain. Max references carb ice charts and highlights how even VFR conditions can require IFR-like vigilance, especially during nighttime descents.The episode wraps with Rob pointing out a discrepancy between NTSB and FAA data on the aircraft’s engine model, and Max reminding pilots that modifying aircraft with STCs can create documentation mismatches.

Max Trescott and Rob Mark return for Episode 4 of NTSB News Talk with critical analysis and commentary on recent aviation accidents and safety investigations. The show kicks off with an update on the fatal Air India Flight 171 crash involving a Boeing 787, which resulted in 241 onboard deaths and 19 fatalities on the ground. A single survivor remains, and while early speculation surrounds the Ram Air Turbine deployment and potential engine failure, official conclusions await India's preliminary report, expected in three months.The discussion then shifts to the LEAP-1B engine bird strike incidents involving Southwest Airlines Boeing 737 MAX jets. Both flights suffered bird ingestion leading to severe cockpit smoke—traced to a design issue where the Load Reduction Device (LRD) triggered an oil leak into the bleed air system. Though the FAA downplayed the threat, the NTSB issued a safety bulletin highlighting the potential risk, drawing parallels to the MCAS issue that plagued earlier MAX crashes.Next, Max recaps the San Diego Citation S550 crash, which occurred during an LNAV approach at night. The pilot descended well below minimums—possibly misreading a military-only value of 500 feet on the approach chart. With no weather reporting available at Montgomery Field and several human factors at play, fatigue and poor decision-making appear to have contributed to the crash.In Broomfield, Colorado, a Beechcraft Travel Air crashed after the pilot reported a door pop shortly after takeoff. The pilot flew an abnormally low pattern and lost control during the downwind leg, possibly due to a stall induced by slowed airspeed. Max and Rob stress that open doors are not emergencies and urge pilots to fly a normal pattern and maintain aircraft control.Rob covers a fatal floatplane crash near Beaver Island, Michigan, where a homebuilt Avid Magnum impacted water during a low sightseeing pass. Though conditions were reported clear, satellite imagery later revealed smoke and haze that likely obscured the horizon. The glassy water conditions and lack of instrumentation may have contributed to the pilot's inability to perceive altitude, a classic seaplane hazard.The show also reviews the in-flight breakup of a Cessna 182 in Reliance, Tennessee, caused by continued flight into a thunderstorm and turbulence beyond the aircraft’s maneuvering speed. Shockingly, the aircraft’s BRS parachute was deployed but not connected properly to the structure, rendering it useless.Finally, the episode covers a Cessna 182RG crash in North Carolina. Witnesses reported an excessively nose-high attitude during a soft field takeoff attempt. The airplane stalled and crashed after barely lifting off. Investigators determined that the pilot likely failed to properly set the elevator trim before takeoff. Toxicology revealed the presence of Zyrtec, a sedating antihistamine, which Max points out is among the FAA’s “no-go” medications for pilots.Throughout the episode, Max and Rob provide context, safety takeaways, and lessons learned that apply to general aviation pilots. Topics include fatigue, medication safety, proper emergency procedures, and the importance of weather briefings and adherence to approach minimums.