Florida Learjet Crash: Reconstructing the Final Minutes and the Evidence
The crew reported manageable icing and turbulence before a sudden, fatal descent exceeding 32,000 feet per minute.8,18
Investigators are now determining whether parts separated before the aircraft struck a road near a mobile home park, forcing hundreds to evacuate.1,7
An earlier version incorrectly described the flight’s Part 91-versus-Part 135 status as unresolved, despite reporting the NTSB’s identification of the flight as a Part 135 charter. Those passages have been corrected; primary flight-specific operational records remain unpublished.
Verification: AVweb coverage of the NTSB briefing · Boca Post’s report of the briefing
- A Learjet 60 carrying nine people crashed in a residential area of Palm Beach County, Florida, on November 1, 2026, after its crew reported light icing and moderate turbulence, then declared an emergency and descended at rates exceeding 20,000 feet per minute.8
- The NTSB has not determined whether the reported icing or turbulence contributed to the event, whether the aircraft first lost control and subsequently exceeded its design limits, or if an external, structural, or equipment event precipitated the loss of control.1
- The aircraft involved was a Learjet 60, serial number 271, manufactured in 2004 and registered as N722BD. FAA registry records, as reported by multiple outlets, list the registered owner as LR60271 LLC, a Delaware limited liability company based in Wilmington, with a registration certificate issued in January 2023 and valid until January 2030. The registry does not disclose the individuals behind the company.6,29
- The FAA said the aircraft descended from 35,250 feet to 8,750 feet in the final minute before striking the ground near Military Trail and 10th Avenue North at approximately 12:50 p.m. EST (17:50 UTC).37
- The final communications between the Learjet 60 and Miami Air Route Traffic Control Center, captured by LiveATC.net and reported by The New York Post and WPBF, began at approximately 12:47 p.m. Eastern Time. A female pilot reported, “We have light, clear ice that is manageable and moderate turbulence,” with altitude deviations of about 700 feet and an outside air temperature of minus 47 degrees Celsius at 35,000 feet.4,8
A Learjet 60 carrying nine people crashed in a residential area of Palm Beach County, Florida, on November 1, 2026, after its crew reported light icing and moderate turbulence, then declared an emergency and descended at rates exceeding 20,000 feet per minute.8
All aboard died, and one person on the ground was injured, according to the National Transportation Safety Board.1,14
At a briefing the next day, NTSB board member Tom Chapman said investigators have evidence the aircraft may have begun breaking apart before impact, but stressed the investigation is in its early stages and no cause has been determined.1
Nine Killed in Florida Learjet Crash; NTSB Cites Possible Pre-Impact Breakup
The NTSB has not determined whether the reported icing or turbulence contributed to the event, whether the aircraft first lost control and subsequently exceeded its design limits, or if an external, structural, or equipment event precipitated the loss of control.1
Aircraft, Owner, Operator and Crew: Certified Facts Versus Unknown Records
The aircraft involved was a Learjet 60, serial number 271, manufactured in 2004 and registered as N722BD. FAA registry records, as reported by multiple outlets, list the registered owner as LR60271 LLC, a Delaware limited liability company based in Wilmington, with a registration certificate issued in January 2023 and valid until January 2030. The registry does not disclose the individuals behind the company.6,29
ABC News reported, citing unspecified records, that the plane belongs to a private company and has been used as a rental in the past.20
The NTSB’s official investigation page for ERA27MA026 states the Learjet 60 was operated by Aurora Aviation doing business as Upper Jets. At the November 2 briefing, NTSB board member Tom Chapman said the flight was a Part 135 charter carrying two pilots and seven passengers.12,40
This conflicts with other data aggregations. PlaneCrashData.com lists LR60271 LLC as the “operator” of N722BD, a conflation of registered owner with operational control that does not mention Aurora Aviation or Upper Jets.5
FAA-derived operator records show N722BD was authorized for commercial charter under Aurora Aviation’s Part 135 certificate, and the aircraft appears on charter listings associated with the company. Independent accounts of the November 2 NTSB briefing identify this specific flight as a Part 135 charter. The aircraft's FAA charter authorization alone would not establish the status of any individual flight. Austin-Bergstrom International Airport spokesman Jim Reynolds described N722BD as a “private aircraft,” a description that does not settle the regulatory question.45
The two crew members have been identified by family members and news outlets, but not officially confirmed by the NTSB. Co-pilot Nathalia Gadelha Filgueiras, 20, was identified by her mother, Camila Corteleti, and stepfather to the New York Post. Her father, Allan Filgueiras, confirmed her identity and co-pilot role to NBC 6. Pilot Jeff Gregory, 55, was identified by family members to TMZ.9,16,28
FAA records obtained by The US Sun show Jeffrey Gregory held an Airline Transport Pilot certificate issued October 1, 2021, with a Learjet 60 type rating and no pilot-in-command restriction on that aircraft. The same records show Nathalia Filgueiras held a Commercial Pilot certificate with an LR-60 type rating that carried a pilot-in-command limitation, consistent with a co-pilot role.23
NBC 6 reported that Filgueiras’ pilot’s license showed she held the rating to fly the jet but not to be in command of the flight. She earned her private pilot’s license at age 17 through a Palm Beach County School District aviation academy program, her family said.15,16
Flight from Austin to the Bahamas: Route, Timing and Last Position
The FAA said the aircraft descended from 35,250 feet to 8,750 feet in the final minute before striking the ground near Military Trail and 10th Avenue North at approximately 12:50 p.m. EST (17:50 UTC).37
FlightAware’s registration record, sourced from the FAA registry, lists the registered owner as LR60271 LLC of Wilmington, Delaware, and identifies N722BD as a Learjet model 60, serial number 271, with 11 seats and 2 turbofan engines.6
The same FlightAware record shows the registration status as 'Assigned,' with a certificate issue date of 2023-01-04, expiration 2030-01-31, and a last action date of 2026-04-01.6
FlightAware’s record lists the airworthiness class for N722BD as 'Unknown/Unknown,' meaning this page does not itself document the aircraft’s airworthiness certificate class or date.6
What is not established is the precise, continuous flight path from Austin to the point of the rapid descent. The available tracking data is fragmented, and the exact route through the reported convective weather near Wellington, Florida, has not been publicly reconstructed from primary radar sources.31
Final 10 Minutes: ATC Communications, ADS-B Reconstruction, Independent Video and Uncertainties
The final communications between the Learjet 60 and Miami Air Route Traffic Control Center, captured by LiveATC.net and reported by The New York Post and WPBF, began at approximately 12:47 p.m. Eastern Time. A female pilot reported, “We have light, clear ice that is manageable and moderate turbulence,” with altitude deviations of about 700 feet and an outside air temperature of minus 47 degrees Celsius at 35,000 feet.4,8
The crew then reported picking up precipitation and requested a climb to 37,000 feet, which the controller approved. Less than 30 seconds later, according to NTSB board member Tom Chapman’s account at the November 2 briefing, a transmission from the airplane announced the descent, followed by a mayday call.1,2
The subsequent emergency transmissions, as transcribed by The New York Post from the audio, escalated rapidly. The pilot stated, “We're descending 8,000 — mayday, mayday — we're descending 10,000 feet per minute,” then declared, “We are in an overspeed condition, descending 20,000 feet per minute,” and later reported, “We are descending 22,000 feet, and we are banking, 60 degrees.” Reuters and The Associated Press, also citing the audio, reported the final words from the cockpit as “We're going to crash into the ground” and “we're out of time.”4,19
ADS-B data cited by PlaneCrashData.com records that the aircraft entered a rapid descent over West Palm Beach and impacted terrain at 17:49 UTC (12:49 p.m. Eastern). Flight tracking data from Flightradar24, reviewed by AeroTime, shows a brief climb at approximately 12:48 p.m. Eastern, followed by a steep descending right turn with a vertical rate exceeding 32,000 feet per minute.5,42
End Time Headlines, citing BocaNewsNow.com, reported that radar data examined before it was removed from tracking sites showed the Learjet at just over 8,000 feet when video footage indicated the aircraft “spiraled, then plummeted nearly nose-first to the ground, resulting in a huge explosion.”31
Independent video evidence includes dashcam footage that circulated online, showing the aircraft in a near-vertical, nose-down dive moments before impact. AeroTime reported that still frames from such video appear to show the Learjet missing its horizontal stabilizer, though this observation has not been confirmed by investigators.17,42
Significant uncertainties remain about the exact sequence and timing. The precise moment the descent began relative to the crew’s climb request is not established, with tracking data and ATC audio providing approximate, non-synchronized timelines. The identity of the pilot speaking on the radio has not been confirmed by the NTSB, though co-pilot Nathalia Filgueiras’s mother, Camila Corteleti, and stepfather identified her as the co-pilot to the New York Post.12,27
Furthermore, the relationship between the reported overspeed condition and the initiation of the rapid descent is unclear. The crew’s declaration of an overspeed came after reporting the descent, leaving open whether the overspeed was a cause or a consequence of the loss of control. The NTSB has not determined whether the aircraft entered a thunderstorm cell, as suggested by some meteorological analyses, or if the reported icing and turbulence were merely conditions present before a separate mechanical or control failure.26,30
Weather in Three Dimensions: Archived Radar, Icing, Turbulence and Pilot Reports
The Learjet 60’s final minutes coincided with a rapidly developing thunderstorm near its flight path over Palm Beach County. MyRadar Weather senior meteorologist Matthew Cappucci, in a timeline review cited by The Tennessean and The Palm Beach Post, placed a thunderstorm cell near the aircraft’s route, noting it grew from approximately 33,000 feet at 12:36 p.m. Eastern to 48,300 feet by 12:56 p.m.26,33
Cappucci’s analysis, as reported by The Tennessean, indicated that at 12:48 p.m., the first officer requested a climb from 35,000 to 37,000 feet, citing increased precipitation, and the mayday call came roughly 20 seconds later. The Economic Times, citing the same MyRadar analysis, noted these measurements do not establish the storm’s exact height when the aircraft passed through the area or prove the storm caused the crash.26,30
Total Pro Sports reported, citing a Live Storm Chasers social media post analyzing Miami radar, that the Learjet flew into a thunderstorm core at 35,000 feet near Wellington at about 12:48 p.m., with radar echoes around the jet reaching 34 dBZ and a 52 dBZ core below it. The same post, according to Total Pro Sports, stated tracking data showed the jet climbing about 450 feet inside the storm core before spiraling downward 76 seconds later.36
The crew’s own reports, captured on air traffic control audio, documented specific conditions. At about 12:47 p.m., a pilot told Miami Center they had “light, clear ice that is manageable and moderate turbulence,” with altitude deviations of up to 700 feet and an outside air temperature of minus 47 degrees Celsius at 35,000 feet, as reported by the NTSB’s Tom Chapman and multiple news outlets.1,8
The reported temperature of minus 47°C is significant for icing potential. The National Oceanic and Atmospheric Administration’s National Centers for Environmental Information (NCEI) documents that its archived NEXRAD radar data includes Level-III products like Hydrometeor Classification and Melting Layer products designed for tracking icing conditions above the surface. However, no specific archived radar data product for the exact time and location of the flight has been published in the available claims.46
International Business Times UK reported that a National Weather Service observation taken about 15 minutes before the crash recorded thunderstorms, three miles of visibility, and winds gusting to 19 knots near the crash site, with a stalled frontal boundary pushing freezing cloud tops tens of thousands of feet high.35
DeWitt Ingram, a Learjet-qualified captain and president of Par-Avion Group Aviation Consulting, told CBS12, as reported by International Business Times UK, that flying into rough air near a thunderstorm’s top could damage an aircraft and cause loss of control, with speed and airframe stress climbing quickly in a subsequent uncontrolled descent.35
What is not established is the precise three-dimensional meteorological environment the aircraft encountered at FL350 in the moments before its descent. While radar analyses and pilot reports indicate proximity to a growing thunderstorm and conditions conducive to clear icing, the exact severity of turbulence, the specific type and accumulation rate of ice, and whether the aircraft penetrated the storm’s core remain undetermined. The NTSB’s Tom Chapman said at the November 2 briefing that investigators could not confirm the plane went into a thunderstorm but were looking at that as part of their investigation.26,33
Extreme Descent, Overspeed and Aircraft Limits: Competing Sequence Hypotheses
The Learjet 60’s final descent was characterized by extreme rates and an overspeed condition, as documented by air traffic control audio and flight tracking data. The crew reported descending at 10,000, then 20,000, and finally 22,000 feet per minute while banking 60 degrees, according to recordings captured by LiveATC.net and reported by The New York Post and The Tennessean.4,26
Flight tracking data reviewed by Flightradar24 indicated the vertical descent rate eventually exceeded 32,000 feet per minute, with the final received altitude recorded as 8,750 feet at 12:49:22 p.m. Eastern Time, as reported by AeroTime, The Economic Times, and Yahoo.41,42,43
The FAA stated the aircraft descended from 35,250 feet to 8,750 feet in a little over a minute—roughly 350 feet per second, or about 21,000 feet per minute—before impact, as reported by ABC News and HNGN.20,25
The crew’s report of an “overspeed condition” during the descent raises questions about the aircraft’s behavior relative to its design limits. The Economic Times, citing an Aerospace Global News report, noted that Mach tuck—a nose-down pitching tendency under certain high-speed conditions—is one possible aerodynamic effect associated with an overspeed, but stated the crew’s report alone does not show Mach tuck occurred or explain how the descent began.30
Aviation experts offered competing hypotheses for the sequence of events. DeWitt Ingram, a Learjet-qualified captain and president of Par-Avion Group Aviation Consulting, told CBS12, as reported by International Business Times UK, that entering rough air near a thunderstorm’s top could damage an aircraft and cause loss of control, with a subsequent uncontrolled descent increasing speed and airframe stress.35
In contrast, Miami-based aviation attorney Zachary Gorwitz of the Podhurst Orseck law firm told The Miami Herald that after reviewing the air traffic control audio, he believed an icing issue, possibly affecting the horizontal stabilizer, may have caused the crash rather than an engine failure, noting “there was no gliding here” and the descent was “incredibly fast.”39
Retired U.S. Navy fighter pilot Matthew ‘Whiz’ Buckley told The Tennessean he estimates the aircraft struck the ground at about 500 mph in a nosedive and, after slowing down video of the impact, believes parts of the tail are missing. He said he does not know whether a flight data recorder could survive such an impact.26
What is not established is the causal sequence: whether the aircraft first lost control due to weather, mechanical failure, or flight control issues and subsequently exceeded its design speed limits, or whether an initial overspeed or structural failure precipitated the loss of control. The NTSB has not determined the relationship between the reported icing and turbulence, the overspeed declaration, and the onset of the rapid descent.30
NTSB Possible In-Flight Breakup: Physical Evidence and Rival Interpretations
At the November 2 news conference, NTSB board member Tom Chapman said investigators have “some evidence that there was some breakup of the aircraft before impact,” citing the distribution of debris as an indication, not a determination of cause.12
NTSB investigator-in-charge Timothy Monville said the debris field measured about half a mile by four-tenths of a mile, spanning ball fields, businesses, and homes, with some pieces possibly farther from the impact point.22
Eyewitnesses at the scene described a lack of large aircraft parts. Anthony Blackmon, an 18-year-old high school student living less than 100 yards from the crash site, told the New York Post he found only small pieces of metal and human remains, saying “the plane seemed completely disintegrated; there were only small parts.”9
The New York Post reported, citing unnamed NTSB investigators, that “early indications suggest the plane may have even started breaking up during its descent.”9
The NTSB has not determined whether components separated before impact as a primary event or as a consequence of the extreme forces during the descent. Chapman, when asked whether the horizontal stabilizer had come off, did not confirm which components might have separated, stating, “We're still seeking to determine that.”12
WPBF reported that NTSB investigators confirmed some parts of the jet separated before impact, while stating the NTSB has not determined whether something failed aboard the aircraft or whether the extreme forces of the descent caused parts to break away.13
What is not established is the timing and mechanism of any structural separation. Investigators have not identified which specific parts were found away from the main crater, nor have they determined if a pre-impact breakup initiated the loss of control or was a result of it. The water-filled impact crater is hampering access to the main wreckage, delaying the examination needed to make those distinctions.12
Learjet 60 Maintenance, Inspection and Relevant Accident History
The NTSB’s investigation of the Scottsdale, Arizona, runway excursion of a Gates Learjet 35A on February 10, 2025, led to urgent safety recommendations concerning the main landing gear of applicable Learjet models. The NTSB’s preliminary report for investigation WPR25FA088 states the flight was operated as a Title 14 Code of Federal Regulations Part 91 corporate flight, resulting in one fatality and multiple serious injuries.11
On October 29, 2025, the NTSB issued urgent safety recommendation A-25-038 to the FAA, requiring operators and owners of applicable Learjet models to comply with a series of Bombardier Service Bulletins concerning the secure attachment of Learjet main landing gear as a condition of continued airworthiness. A second recommendation, A-25-039, asked the FAA to require Bombardier to revise maintenance procedures for those models to include a check of the aft landing gear trunnion pin and retaining bolt position after gear maintenance requiring aft trunnion removal.11
The NTSB’s news item accompanying those recommendations, dated October 29, 2025, was headlined 'NTSB Issues Urgent Recommendation on Learjet Landing Gear' and stated that main landing gear could separate on landing.11
Military.com reported that Tempus Jets announced in June 2016 a five-year Navy threat-simulation contract involving Learjet 35A and Learjet 60 aircraft, but noted that nothing in public records ties the crashed jet N722BD to any military history or contract work.3
The US Sun reported obtaining audio of an incident in May 2026 near Newark, New Jersey, involving the same aircraft, N722BD, in which a female pilot reported 'moderate chop' and an inability to hold altitude, and a controller replied, 'If you can't maintain altitude, that's not moderate. That's severe turbulence.' The outlet noted the exchange was first reported by MailOnline from the ATC App, and that the identities of the pilots heard—including whether the woman was co-pilot Nathalia Filgueiras—have not been confirmed. The NTSB has not indicated whether this prior event is part of its investigation.23
What is not established is whether any prior maintenance issues, airworthiness directives, or service bulletins were applicable to N722BD or were complied with. The FAA registry record for N722BD, as displayed by FlightAware, lists the airworthiness class as 'Unknown/Unknown' and provides no operator, airworthiness directive, or maintenance information.6
The relevance of the 2025 Scottsdale accident and the subsequent landing gear recommendations to the November 2026 Florida crash is not established. The NTSB has not indicated any connection between landing gear security and the in-flight breakup evidence cited in the Florida investigation.11
Victims, Impact Scene, Ground Injuries and Evacuation
The identities of those killed have not been officially released by the NTSB or the Palm Beach County Medical Examiner's Office. However, family members have provided identifications to news outlets. A joint statement from the Robinson, Sharp, Reed, Fehr and Cetina families, published by WPBF and The Palm Beach Post, identified the seven passengers as Adam Robinson, 45, his wife Helen Sharp, 40, their children Emma, 4, and Charlie, 2, the children's nanny Anita Maria Cetina, and family friends Rachael Reed and Charmi Fehr.32,34
The two crew members were identified by family members as pilot Jeff Gregory, 55, and co-pilot Nathalia Gadelha Filgueiras, 20. Filgueiras's stepfather, Thiago Corteleti, confirmed her identity and role to WPBF, and her father, Allan Filgueiras, confirmed it to NBC 6. Gregory was identified by family members to TMZ.16,28,32
The impact scene was described by officials and witnesses as catastrophic. Florida Governor Ron DeSantis, visiting the site Sunday evening, said the crash was 'cataclysmic' and 'looked like a missile going down,' leaving a large crater on the side of Military Trail and scattering debris across a significant area.7,8
Eyewitness Anthony Blackmon, an 18-year-old living less than 100 yards away, told the New York Post he found human remains and small aircraft fragments scattered across the scene, but 'no big parts' of the plane, saying 'the plane seemed completely disintegrated.' Palm Beach County Commissioner Joel Flores told the New York Post that wreckage was piled on the rooftops of mobile homes closest to the impact zone.9,10
Officials provided conflicting accounts of injuries on the ground. At the Sunday news conference, Palm Beach County officials said they had not received reports of anyone on the ground being killed or injured. However, at the November 2 briefing, NTSB investigator-in-charge Timothy Monville said one man in a vehicle 'immediately adjacent' to the crash site sustained a leg injury.1,7
The crash forced the evacuation of approximately 600 residents from the nearby Cresthaven mobile home community, as the debris field blocked the only entrance. Palm Beach County Commissioner Joel Flores said residents were bused to a shelter at the Greenacres Community Center, with around 50 people staying overnight. Military Trail between 10th Avenue North and Purdy Lane/Alameda Drive was closed indefinitely.7,10,44
What is not established is a definitive timeline for residents to return home or for the roadway to reopen. Commissioner Flores told WPTV it 'could be up to two weeks' before residents return, as the area remains an active investigation site. The NTSB's Monville noted that recovering the main wreckage from the water-filled impact crater would be a several-day process.21,24
What Investigators Will Test Next: Recorders, Wreckage, Weather and Unanswered Questions
The NTSB’s immediate investigative priorities, outlined at the November 2 briefing, focus on recovering physical evidence and constructing a precise chronology. Investigator-in-Charge Timothy Monville said recovering the major wreckage from the water-filled impact crater on Military Trail would be a several-day process, hampered by heavy rainfall. NTSB board member Tom Chapman added that maintenance records indicate a cockpit voice recorder was installed on the aircraft, but investigators do not yet know whether it was still aboard or can be recovered.12,21
The debris field itself, measuring roughly half a mile by four-tenths of a mile according to Monville, is a primary dataset. Investigators will map the location and identity of each recovered piece to determine if components separated before impact, as Chapman indicated was a possibility. This analysis will seek to distinguish whether a structural failure precipitated the loss of control or was a consequence of the extreme aerodynamic forces during the reported descent exceeding 32,000 feet per minute.13,22
Weather reconstruction will rely on archived NEXRAD radar data to build a three-dimensional model of the thunderstorm cell near Wellington, Florida, that meteorologist Matthew Cappucci analyzed for MyRadar. The NTSB’s Tom Chapman said investigators could not confirm the plane went into a thunderstorm but were looking at that as part of their investigation.26,46
A critical task is reconciling all available timing data into a single, authoritative chronology, synchronizing air traffic control audio, primary radar tracks, and ADS-B data.1
The investigation will examine the aircraft’s maintenance and operational history, including compliance with applicable Airworthiness Directives and the underlying operational-control records for the reported Part 135 charter.11,45
Pilot qualifications and crew actions will be scrutinized using FAA records and training documentation.23
Several decisive questions remain unanswered and will guide the investigation. The flight was identified as a Part 135 charter at the November 2 NTSB briefing, although the agency's brief initial written investigation page does not specify the regulatory category. The exact sequence—whether control was lost first, exceeding design limits, or if an external, structural, or equipment event precipitated the loss of control—is unknown. The identity and certification status of the pilot-in-command during the emergency is not confirmed, nor is the status of any cockpit voice recorder. Officials must also reconcile the first-day reports of no ground injuries with the NTSB’s November 2 update citing one leg injury.13,38,45
The NTSB’s final report will depend on the integration of these disparate evidence streams: wreckage analysis, recorder data if recovered, meteorological reconstruction, ATC and radar timelines, maintenance records, and crew history. Until that synthesis is complete, the cause of the rapid descent and the significance of the indicated pre-impact breakup remain formally undetermined.1
Learjet 60 N722BD departed Austin-Bergstrom International Airport in Texas bound for North Eleuthera Airport in the Bahamas at 15:37 UTC (10:37 a.m. EST), according to ADS-B data cited by PlaneCrashData.com.5
A female pilot told Miami Air Route Traffic Control Center the aircraft was at 35,000 feet experiencing 'light, clear ice that is manageable and moderate turbulence,' with altitude deviations of about 700 feet and an outside air temperature of minus 47 degrees Celsius, according to NTSB board member Tom Chapman.1
The crew reported precipitation and requested a climb to 37,000 feet, which air traffic control approved, Chapman said.1
A transmission from the airplane announced it was descending, followed by a mayday call, Chapman said.1
The crew transmitted, 'We are in an overspeed condition, descending,' with the rest unintelligible, according to Chapman's account.1
In air traffic control audio captured by LiveATC.net, a pilot declared, 'Mayday, mayday, we're descending 10,000 feet per minute,' then reported an overspeed condition and a descent of 20,000 feet per minute, according to The New York Post.4
Flight tracking data from Flightradar24 showed a vertical descent rate exceeding 32,000 feet per minute and a final received altitude of 8,750 feet at 12:49:22, according to AeroTime.42
The Learjet 60 crashed near the intersection of Military Trail and 10th Avenue North in the Greenacres/Cresthaven area of Palm Beach County, according to the FAA.8
U.S. Transportation Secretary Sean Duffy confirmed on X that all nine people aboard died.8
Florida Governor Ron DeSantis, visiting the scene, described the crash as 'cataclysmic' and said it 'looked like a missile going down,' leaving a large crater. He said officials had no reports of injuries on the ground at that time.8
At an afternoon news conference, NTSB board member Tom Chapman said investigators have 'some indication that the aircraft was breaking up before impact.'1
NTSB investigator-in-charge Timothy Monville said one man in a vehicle adjacent to the crash site sustained a leg injury, revising earlier statements that reported no ground injuries.1
- The flight-specific charter documentation and operational-control records underlying the NTSB's reported Part 135 designation.
- The exact sequence and cause of the rapid descent and overspeed: whether control was lost first, exceeding design limits, or if an external/structural/equipment event precipitated the loss of control.
- The identity and certification status of the pilot-in-command (Jeffrey Gregory vs. Nathalia Filgueiras) and confirmation of who was at the controls during the emergency.
- The status and recovery of any cockpit voice recorder or flight data recorder; installation is indicated per maintenance records, but recovery/aboard status is unconfirmed.
- Reconciliation of the first-day official statements (Gov. DeSantis) reporting no ground injuries with the NTSB's Nov. 2 update reporting one leg injury on the ground.
- The precise meteorological conditions (icing type, turbulence severity, storm cell interaction) experienced by the aircraft at FL350 at the time of the event, as distinct from nearby weather observations and later analyses.
- 1.
- 2.
- 3.
- 4.
- 5.Secondary reportplanecrashdata.com — N722BD Crash Report (2026) — PlaneCrashData
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19.
- 20.
- 21.
- 22.
- 23.
- 24.
- 25.Original reportinghngn — Learjet Nosedives Into Palm Beach County Road, Killing All 9
- 26.
- 27.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.Primary documentntsb.gov — ERA27MA026.aspx - ntsb.gov
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.