What is confirmed about November 18
The named reports concern events in Kentucky, Puerto Rico, Florida, Louisiana, and Oregon, as well as historical investigations. The NTSB report on TWA Flight 800 and the FAA report on Starship Flight 7 concern historical investigations; the Cessna 210 crash and Alaska Airlines return described in the reports occurred on April 2. None of these named reports describes a November 18 event in Newport Beach. They give you a narrower answer: several aviation events and older accident records are documented.
As of 14:49 UTC on November 19, 2026, the reported events and investigation records fall into three categories:
- Confirmed event details: facts tied to an identified aircraft, flight, location, date, or official record.
- Preliminary or attributed reporting: information reported by a news organization or aviation publication while details may still change.
- Unknown or unverified information: a claim that lacks a confirmed date, location, aircraft identity, consequence, or official status.
The Federal Aviation Administration and National Transportation Safety Board remain the appropriate places to check for later accident statements, investigation pages, and updates.
Older material can still help you understand how an official record is structured. It cannot, by itself, answer what happened on November 18.
Confirmed official records are not the same as yesterday’s event
The September 6, 2026 NTSB record concerning 21 Air flight 7598 is an example of a confirmed accident record, but it is not evidence of an accident on November 18. The record states that, at about 1:53 p.m. eastern daylight time, the Boeing 767-33A overran runway 30 after landing at Miami International Airport and struck two ground passenger vehicles. The flight was a domestic cargo operation for Amazon.com Services LLC under Title 14 Code of Federal Regulations Part 121, traveling from San Juan, Puerto Rico, to Miami.
The NTSB record identifies consequences by group rather than leaving the term “casualties” undefined. The two crewmembers sustained minor injuries; five people on the ground sustained fatal injuries; and three people on the ground sustained serious injuries. Those figures describe the September 6 Miami accident and do not describe November 18.
Historical maintenance material illustrates the same need for date discipline. In one accident record, the Safety Board found three logbook entries regarding fuel leaks during the two years preceding the accident. The airplane also had several intermittent fueling problems during those two years, including one before departure from JFK. Those findings belong to that historical investigation, not to a current airplane or flight.
A spaceflight record is another example of why classification matters. The FAA-required investigation of the SpaceX Starship Flight 7 mishap on January 16 was closed, and the record described no public injuries and one confirmed report of minor vehicle damage in the Turks and Caicos Islands. That was a spaceflight mishap, not a confirmed airplane accident on November 18.
The practical test is simple: match the event date, location, aircraft or operation, and official record before treating an entry as yesterday’s accident.
Separate a crash, an injury event, and a report
The Kentucky UPS report and the JetBlue turbulence report describe materially different events, so you should not place them in the same “plane crash yesterday” category without checking their dates and details.
The Associated Press reported that a large UPS cargo plane with three people aboard crashed while taking off from an airport in Louisville, Kentucky, and ignited an explosion and massive fire. A separate AP headline reported that at least 12 people died after an engine fell off the UPS plane before the crash and explosion, including a child. The number of people aboard and the reported death toll describe different groups; the report does not say that all 12 people were aboard the aircraft.
The same AP reporting said that the aircraft’s left wing caught fire and that an engine fell off before the crash. Those details were reported investigative information, not a final finding about cause or fault. Federal investigators were expected to examine the engines and maintenance records.
The JetBlue report described an A320-200 operating as flight B6-1717 from Ponce, Puerto Rico, to Fort Lauderdale, Florida, on November 17, 2026. The Aviation Herald reported that severe turbulence caused injuries to five people on board. The aircraft continued to Fort Lauderdale and landed safely on runway 10L. The airline reported that medical personnel evaluated customers and crew members and that none was taken to a hospital.
That JetBlue event involved reported injuries and a safe landing; the report describes it as a turbulence event rather than a crash. The Kentucky event was described as a crash and explosion. Neither report proves that the event occurred on November 18. A social-media post that supplies a different date, aircraft, death toll, or cause remains unverified until an authoritative or reliable report supports it.
What remains unconfirmed about November 18
The April 2 Louisiana and Oregon events cannot answer the November 18 question because their dates, places, and event descriptions belong to earlier reporting. They also show which facts you need before accepting a new airplane-accident report.
A Cessna 210 was reported to have crashed near Houma-Terrebonne Airport in Louisiana at about 8:30 p.m. local time on Wednesday, April 2. Two people were aboard. The FAA and National Transportation Safety Board were to investigate, with the NTSB in charge and expected to provide further updates.
The same FAA accident-and-incident material described an Alaska Airlines event rather than a crash. Alaska Airlines Flight 757 returned safely to Portland International Airport at about 9:50 a.m. local time on Wednesday, April 2, after the crew reported fumes in the flight deck. The Boeing 737-800 had been heading to Harry Reid International Airport in Las Vegas, and the FAA was to investigate the event.
For a reliable November 18 update, look for all of these details:
- the calendar date and local time, including the relevant time zone;
- the location and airport, if known;
- the aircraft, flight number, or operation, if confirmed;
- whether the report describes a crash, injury event, emergency return, or another occurrence;
- confirmed information about injuries, deaths, or property damage; and
- the agency responsible for the investigation and its latest public status.
A report that lacks those details may still be an early lead, but it should not be presented as a confirmed November 18 accident. A social-media claim about an additional accident remains unverified.
Use FAA and NTSB updates for the next status check
FAA and NTSB updates matter because an investigation can replace an early description with a more precise account. A news report may accurately describe what officials had learned at one point without establishing the final cause, responsibility, or legal result.
In the Kentucky UPS crash, AP reported that federal investigators planned to examine the aircraft’s maintenance records and engines after an engine fell off during takeoff. That planned review identifies evidence investigators intended to examine; it does not establish why the engine separated or who may be responsible.
In the Florida Learjet crash, investigators found pieces of the elevator, a tail component that controls pitch, more than a mile from the main crater. The reported location of those pieces confirmed that the plane began breaking apart before impact. That finding describes one physical part of the investigation. It does not, by itself, answer every question about cause or liability.
The FAA identifies a list of 10 most frequent causal factors for general aviation accidents involving the pilot in command and states that the list remains relatively stable. That general safety material can provide context, but it cannot identify the cause of a particular November 18 event.
Use this order for a later status check:
- Look for an FAA accident or incident statement.
- Look for an NTSB investigation page or record when the NTSB is involved.
- Compare the agency’s date, location, aircraft, and consequence details with the original report.
- Treat cause, fault, casualty totals, and legal conclusions as unresolved unless the responsible authority has established them.
The FAA’s acceptance of findings in a separate SpaceX Starship Flight 7 investigation and its continuing oversight of the Starship Flight 8 investigation show why an investigation’s status must be checked directly rather than assumed from an older report.
If you may be involved, protect health and the record first
Your health and the basic incident record come before trying to determine fault. If you or a family member may have been involved in an aviation accident or injury event, take these practical steps:
- Obtain medical care. If there is immediate danger, serious injury, or another medical emergency, contact emergency services promptly. For non-emergency needs, seek prompt medical attention for an injury or continuing symptom. After an aviation accident, you should document what happened, seek medical care, and consult an attorney to assess your claim.
- Report the injury. Report an injury to the airline or responsible operator when appropriate, and keep a copy or record of what you reported.
- Preserve the basic file. Keep medical records, incident reports, and witness statements together. Gathering those materials is vital for substantiating a claim after an airplane crash.
- Write down what you remember. Record the flight or operation, date, location, sequence of events, symptoms, treatment, and names of witnesses while the details are still available. Do not change the account to fit a later theory.
- Avoid public speculation. Do not post accusations or a theory about fault as though it were established. Early reports can change, and an investigation may still be collecting physical and documentary evidence.
Preserve your own medical and incident information, and seek qualified help if injury or loss is involved.
Understand the investigation timeline before drawing conclusions
An aviation investigation develops in stages, so an early report and a final report answer different questions. Investigators may examine physical wreckage, aircraft components, maintenance records, engines, operational information, and witness accounts before reaching a final conclusion.
Investigation timing varies by case.
A preliminary update can help identify the aircraft, location, known consequences, and evidence being gathered. It should not be treated as a final determination of cause or legal responsibility.
You do not have to wait for the final report to ask what your options are. Early qualified review can focus on preserving records and identifying questions without treating preliminary information as a final answer.
Seek qualified evaluation when the event caused injury or loss
A qualified aviation-injury evaluation may be appropriate when an event caused hospitalization, continuing symptoms, a death, disputed details, missing records, or uncertainty about how to preserve information. Those circumstances do not establish that you have a claim or identify who is responsible. They do indicate that the facts may require careful review before records change or important questions are overlooked.
General aviation safety material should also be kept in its proper place. The FAA identifies inadequate preflight preparation or planning as one of the 10 most frequent causal factors for general aviation accidents involving the pilot in command. The FAA also identifies improper inflight decisions or planning and selection of unsuitable terrain among that same list of 10 factors.
Those FAA factors describe patterns in general aviation accidents involving the pilot in command. They do not prove that any particular pilot, airline, owner, mechanic, manufacturer, or other party caused a reported event. Do not use a general safety list as a substitute for the facts of the flight and the official investigation.
If you were injured, if a family member died, or if the event details remain disputed, organize the information you have and seek qualified legal review. Bring the flight or operation details, medical records, incident reports, witness information, and communications about the event. An attorney can assess the information you provide and explain what questions require further investigation.
Request a free case evaluation if personal help is needed
If you or a family member may have suffered injury or loss in an airplane accident or other aviation event, preserve the date, flight or aircraft information, medical records, incident reports, and witness details before seeking a review. Keep the November 18 date question separate from the legal questions raised by a particular injury or death. We offer a free case evaluation available 24/7.
Frequently asked questions about airplane accident reports.
How can someone verify whether a reported crash actually happened?
Check the event date and local time, location, aircraft or flight number, event classification, reported consequences, and investigating agency. Then compare those details with an FAA accident or incident statement and, when applicable, an NTSB investigation page. A report that lacks those details should remain preliminary or unverified rather than being treated as a confirmed crash.
Does a safe emergency landing count as an airplane accident?
Not necessarily. A safe return or landing after fumes, turbulence, or another problem may be an incident or emergency rather than a crash. The classification depends on the documented event and applicable aviation records; reported injuries or an emergency response alone do not establish that a crash occurred.
What information should a potentially affected family preserve while an investigation is pending?
Preserve the flight or aircraft information, date and location, medical records, incident reports, witness details, photographs or videos, and communications with the airline or operator. Seek medical care for injuries, report the injury when appropriate, and avoid publicly assigning fault while officials are still gathering evidence. These steps preserve information but do not determine liability or claim eligibility.

Emery Brett Ledger brings 28+ years of experience to personal injury law. He founded & led The Ledger Law Firm in securing over $100 million in compensation for clients with life-altering injuries & complex claims. Licensed in California, Texas, & Washington, Emery earned his law degree from Pepperdine University School of Law. His practice areas include car & truck accidents, wrongful death, catastrophic injuries, maritime claims, & mass tort litigation. He has been recognized by The National Trial Lawyers’ Top 100, Mass Tort Trial Lawyers Top 25, and America’s Top 100 Personal Injury Attorneys. Emery also received the 2025 Elite Lawyer Award & holds a perfect 10.0 Avvo rating with Platinum Client Champion status.
