<?xml version="1.0" encoding="utf-8" ?><rss version="2.0"><channel><title>Speiser Krause in the News and Recent Developments</title><description>Speiser Krause in the News and Recent Developments</description><link>https://speiserkrause.com/lawyer/blog/Speiser-Krause-in-the-News-and-Recent-Developments</link><language>en-us</language><lastBuildDate>Fri, 10 Apr 2026 16:02:39 GMT</lastBuildDate><ttl>10</ttl><item><title><![CDATA[Speiser Krause Monitoring the Investigation into the Runway Crash at LaGuardia Airport Involving Air Canada Express Flight 8646 on March 22, 2026]]></title><link>https://speiserkrause.com/lawyer/2026/04/01/Recent-Developments/Speiser-Krause-Monitoring-the-Investigation-into-the-Runway-Crash-at-LaGuardia-Airport-Involving-Air-Canada-Express-Flight-8646-on-March-22,-2026_bl54467.htm</link><description><![CDATA[<p>On Sunday, March 22, 2026, at approximately 11:40 p.m., Air Canada Express Flight 8646 collided with a fire truck as it landed on Runway 4 at New York’s LaGuardia Airport.&nbsp; The aircraft, a CRJ-900 model aircraft, was operated by Jazz Aviation, L.P., Canada’s largest regional airline.&nbsp; &nbsp;The flight originated from the Montreal-Pierre Elliott Trudeau International Airport in Montreal, Canada, with LaGuardia Airport in Queens, New York, as its final destination.</p>

<p>The flight was uneventful through landing.&nbsp; As the aircraft touched down on Runway 4, fire and emergency equipment were operating on the airport property.&nbsp; A fire truck from a Port Authority Police Department unit known as Truck One and Company contacted the Ground Air Traffic Controller (“Ground Control”) who is responsible for ground movement at the airport.&nbsp; The Aircraft Rescue and Firefighting Truck was responding to a call for assistance involving another aircraft, and asked permission to cross Runway 4 at the Taxiway D (Delta) intersection.&nbsp; Ground Control approved the request.&nbsp; However, at this time Flight 8646 had just landed on Runway 4 and was travelling at a ground speed of approximately 100 miles per hour.&nbsp; As the fire truck began crossing Runway 4, Flight 8646 collided with the truck.&nbsp; Although Ground Control initially approved the fire truck’s request to enter the active runway, the air traffic controller then realized that Flight 8646 was completing its after-landing roll out.&nbsp; Ground Control then attempted to stop the fire truck from crossing Runway 4, directing the truck to “Stop! Stop!” but it was too late and, being unable to stop in time, Flight 8646 collided with the fire truck.&nbsp; It is unknown at this time why Ground Control initially cleared the fire truck to enter and cross Runway 4 with an aircraft cleared to land on the same Runway but communications after the collision indicated that the Ground Controller realized his mistake. The communications between Ground Control and the fire truck can be heard <strong><a href="/global_pictures/firetruck.mp3" target="_blank">HERE</a></strong>.&nbsp; To place these communications into context below is an airport chart depicting the location of the collision at taxiway D and Runway 4.</p>

<p><img src="https://speiserkrause.com/global_pictures/runway.jpg?v2"><br>
<strong>Aerial image from Google Earth</strong></p>

<p>Tragically, the collision sheared the front part of the cockpit from the fuselage.&nbsp; The pilot and co-pilot were killed, and the flight attendant was ejected from the aircraft suffering severe injuries.&nbsp; There were a total of 76 individuals on board Flight 8646, consisting of 72 passengers, the 2-person flight crew and 2 flight attendants.&nbsp; Early reports indicate that 41 persons were initially hospitalized including two occupants of the fire truck, but 31 have since been released.&nbsp; Ten individuals remain hospitalized with severe injuries.</p>

<p>The National Transportation Safety Board (“NTSB”) will be the lead federal agency responsible for conducting the investigation.&nbsp; Parties to the investigation will be the airline, Jazz Aviation, the Federal Aviation, the unions representing pilots as well as the air traffic controllers&nbsp; and possibly the aircraft manufacturer. The NTSB will examine all aspects of the crash including the conduct of Air Traffic Control, the flight crew and the movement of the fire truck.&nbsp; This will include an analysis of the Airport Surface Detection System (“ASD”).&nbsp; The ASD Display is similar to ground radar that provides visual information to air traffic control about the movement of planes and other vehicles on the tarmac. In addition, the “Black Boxes” from Flight 8646 consisting of the Cockpit Voice Recorder and Digital Flight Data Recorder, both of which have been recovered by the NTSB, will shed additional light on the actions of the flight crew, whether the crew even realized that the fire truck entered the Runway, whether it was possible for the crew to undertake evasive action, and what actions the crew took in their attempt to avoid the collision.&nbsp; The NTSB will analyze all available data, including surveillance video which captured the tragic collision in rendering its Factual and Probable Cause findings.</p>

<p><strong>Claims Against the United States of America for the Failures of Air Traffic Control</strong></p>

<p>Speiser Krause has decades of experience litigating against the United States for the failures of Air Traffic Control. Currently the firm represents six families from the midair collision over the Potomac River in January 2025, and several lawyers from the firm have been appointed to the Plaintiffs’ Steering Committee responsible for conducting the litigation on behalf of all passengers. Speiser partner Douglas A. Latto has been appointed Co-Lead counsel in that litigation.&nbsp; The Firm has also represented victims of other midair collisions, including the midair collision the Hudson River, as well as numerous cases resulting from the negligence of Air Traffic Control both in New York and throughout the United States.</p>

<p>Although the United States can be sued for the failures of air traffic control, cases involving ATC involve specialized laws including, but not limited to, the Federal Tort Claims Act (“FTCA”), aviation statutes and regulations including the Federal Aviation Act, as well as the policies and procedures governing the conduct of air traffic control.&nbsp; Unlike private defendants, specific rules must be followed when commencing litigation against the United States.&nbsp; You cannot simply file suit against the United States.&nbsp; Rather, you must first file an Administrative Claim (commonly referred to as a “Form 95”) setting forth your allegations against the government as well as specific requests for damages.&nbsp; You must then wait a certain amount of proscribed time before litigation can be brought.&nbsp; The team at Speiser Krause has extensive experience in this area of the law.</p>

<p><strong>Claims Against the Port Authority of New York/New Jersey</strong></p>

<p>The Port Authority is a bi-state agency that operates and maintains critical transportation infrastructure at various ports within New York and New Jersey, including LaGuardia Airport. The Port Authority is collectively governed by the governors of New York and New Jersey. While it may be too soon to say what responsibility or ability the operator of the Port Authority truck may have had to see and avoid Flight 8646 once cleared to cross Runway 4, Speiser Krause is mindful of the statutory preconditions to suit involving claims against the Port Authority. Like the Federal government, a Notice of Claim is required before suit can be brought against the Port Authority but the time frames are markedly different.&nbsp; Under applicable law, the Port Authority requires that a Notice of Claim must be served on the agency within 10 months of the crash, and requires suit to be filed within one year.&nbsp; In addition, the Notice of Claim must be served no less than 60 days prior to any lawsuit being filed.&nbsp; This is a much shorter period than that within which claims must be filed against a private defendant, or even against the United States. Because these prerequisites are jurisdictional in nature, victims must be careful to meet the stringent requirements prior to filing claims against the agency. Speiser Krause has successfully litigated claims against the Port Authority for decades and is very familiar with these requirements.</p>

<p><strong>Claims Against the Airline</strong></p>

<p>Although it is far too soon to determine whether and to what extent the airline has any responsibility for this tragedy, since this flight involved international travel, a federal treaty known as the Montreal Convention will govern the rights of the passengers. Under the Convention, the airline is strictly liable for damages equal to 100,000 Special Drawing Rights (“SDRs”) assuming that a passenger’s injuries meet or exceed that sum. Certain types of damages, however, may not be recoverable from the airline under the Montreal Convention but may be recoverable from other defendants.&nbsp; &nbsp;The team at Speiser Krause also has extensive experience litigating claims under the Montreal Convention and has been involved in virtually every international aviation disaster impacting US citizens for over fifty years.&nbsp; The Firm also has significant experience in litigating claims against Canadian airlines, including recently resolving a crash that occurred in June 2024 which took the life of one passenger and injured others.</p>

<p>Although the investigation is only beginning, it is unknown if any additional factors, such as fatigue, nighttime conditions, or human performance, contributed to the crash. Although the NTSB will examine all aspects associated with this tragedy, given the speed at which Flight 8646 was travelling as it was landing on Runway 4, it is unlikely that the flight crew could have done much, if anything, to avoid the collision.&nbsp; However, all potential causes must be examined to ensure that a tragedy like this does not happen again.</p>

<p>Speiser Krause will continue to monitor the investigation and provide updates and we are available to answer any questions.</p>]]></description><pubDate>Wed, 01 Apr 2026 09:00:00 GMT</pubDate><category>Blogs</category></item><item><title><![CDATA[Speiser Krause Monitoring the Investigation into the crash of UPS Flight 2976 in Louisville, Kentucky on November 4, 2025]]></title><link>https://speiserkrause.com/lawyer/2025/11/07/News/Speiser-Krause-Monitoring-the-Investigation-into-the-crash-of-UPS-Flight-2976-in-Louisville,-Kentucky-on-November-4,-2025_bl54421.htm</link><description><![CDATA[<p>At approximately 7:23 p.m., on November 4, 2025, a UPS McDonnell Douglas MD-11F Freighter aircraft bearing registration number N259UP, and operated as UPS Flight 2976, departed from Louisville Muhammad Ali International Airport in Louisville, Kentucky and crashed immediately upon takeoff.&nbsp; The UPS cargo flight, which was destined for Honolulu, Hawaii, exploded into flames causing extensive injuries and damage in the debris path.&nbsp; Surveillance video captured the takeoff and crash and demonstrated that the left engine was on fire as the aircraft began to lift off the runway and when it slammed into an industrial area near the airport where several businesses are located.&nbsp; The McDonnell Douglas manufactured aircraft (which has since been taken over by Boeing) had three crew members on board all of whom were killed in the crash.&nbsp; At least 9 ground victims were killed, many more were injured and the authorities in Kentucky believe that the death toll will unfortunately rise.&nbsp; Ground victims also suffered severe burn and blunt impact injuries as a result of the crash and ensuing fire.&nbsp; The fire was extensive as the aircraft carried significant fuel for the flight to Hawaii. The airport in Louisville is the largest hub for UPS, where approximately 400 flights land and depart each day.</p><p>The MD 11 aircraft entered service in 1991 and was originally configured for passenger operations.&nbsp; In 2006 the aircraft was re-configured for cargo operations and has been part of the UPS fleet since that time.&nbsp; Although early in the investigation, it is known that the left engine separated from the aircraft during the takeoff roll and was found on the runway.&nbsp; Several early reports indicated that the flight was delayed due to maintenance issues associated with the left engine which caught fire and separated during takeoff. UPS, however, has since denied those reports, stating that the flight was not delayed nor did it undergo maintenance prior to the flight.&nbsp; The aircraft, however, did undergo extensive maintenance in the month of October, but it is presently unknown the precise nature of that maintenance.&nbsp; This undoubtedly will be a focus of the investigation.<br>The National Transportation Safety Board is on-site and is the lead agency responsible for the accident investigation.&nbsp; Parties to the investigation will include Boeing, as the manufacturer responsible for the aircraft’s type certificate as a result of its takeover of McDonnell Douglas, General Electric, the manufacturer of the three CF6-80C2D1F engines that were installed on the aircraft, UPS (the largest employer in Louisville, Kentucky), as the aircraft operator, as well as the Federal Aviation Administration.&nbsp; Other entities may become parties to the NTSB’s investigation as more facts become known.</p><p>The aircraft’s cockpit voice and digital flight data recorders, known as the “black boxes” have been recovered and sent to the NTSB’s lab in Washington D.C. for analysis.&nbsp; The black boxes will provide significant insight into the cause of this tragedy.</p><p>

<img src="/global_pictures/sp-plane.jpg">

<br><br>Picture of the UPS MD-11 accident aircraft&nbsp;</p><p>Speiser Krause has extensive experience in crashes that have occurred on takeoff due to numerous issues, including, maintenance, aircraft design, and pilot error.&nbsp; &nbsp;Speiser is monitoring the investigation and will provide additional updates as more information becomes available.</p><div></div><p><br /></p>]]></description><pubDate>Fri, 07 Nov 2025 12:13:00 GMT</pubDate><category>Blogs</category></item><item><title><![CDATA[Update Regarding Crash of de Havilland DHC-2 Beaver Aircraft in Ontario, Canada on June 16, 2024]]></title><link>https://speiserkrause.com/lawyer/2025/07/10/Recent-Developments/Update-Regarding-Crash-of-de-Havilland-DHC-2-Beaver-Aircraft-in-Ontario,-Canada-on-June-16,-2024_bl54350.htm</link><description><![CDATA[<p>The Transportation Safety Board of Canada (the “TSB”) recently completed its investigation into the crash of a DHC-2 Beaver aircraft that occurred on June 16, 2024.&nbsp; The aircraft, which is equipped with flotation pontoons, took off from the Chukuni River in Ontario with an intended destination of Thicket Lake.&nbsp; At the time of the crash the four passengers, all Indiana residents, were travelling to a camp site on Thicket Lake for a fishing trip, and the crash occurred immediately after takeoff.&nbsp; The passengers have all retained Speiser Krause to represent them in connection with this tragedy.</p>
<p>As expected, the TSB determined that the crash was caused by pilot error.&nbsp; At the time of takeoff, the aircraft exceeded the Maximum Takeoff Weight (“MTOW”) in violation of applicable operating procedures contained in the Aircraft’s Flight Manual.&nbsp; In addition, immediately after takeoff the pilot improperly and prematurely reduced engine power and retracted flaps in violation of applicable takeoff procedures.&nbsp; As a result, the aircraft entered an aerodynamic stall approximately 100 feet above the water causing it to crash into the river.&nbsp; Tragically, one passenger died as a result of the crash and the others sustained varying degrees of substantial personal injuries.&nbsp;&nbsp;</p><p dir="ltr" style="text-align: justify;">Speiser Krause has extensive experience in international aviation disasters and the Firm is presently pursuing all legal avenues to ensure that the passengers of this tragedy receive the compensation that they rightly deserve.</p>]]></description><pubDate>Thu, 10 Jul 2025 09:56:00 GMT</pubDate><category>Blogs</category></item><item><title><![CDATA[Speiser Krause Investigating the Crash of Air India Flight 171 Boeing 787-8 Dreamliner Airplane Near Ahmedabad, India]]></title><link>https://speiserkrause.com/lawyer/2025/06/16/News/Speiser-Krause-Investigating-the-Crash-of-Air-India-Flight-171-Boeing-787-8-Dreamliner-Airplane-Near-Ahmedabad,-India_bl54339.htm</link><description><![CDATA[<span></span><p dir="ltr" style="text-align: justify;">On June 12, 2025, at approximately 1:43 p.m. local time, Air India Flight 171, a Boeing 787-8 Dreamliner with 242 passengers and crew, crashed shortly after takeoff from Sardar Vallabhbhai Patel International Airport in Ahmedabad, Gujarat, India. The London-bound flight was scheduled to land at Gatwick Airport when it crashed shortly after takeoff.&nbsp; Miraculously, one passenger, Vishwash Kumar Ramesh, who was seated in Seat 11A survived the crash, but his brother, who was also on the London bound flight was tragically killed. Mr. Ramesh advised investigators that immediately after liftoff from the runway he heard a loud bang and then the aircraft crashed.</p><p dir="ltr" style="text-align: justify;">The Dreamliner crashed into a building that was a medical college hostel with early reports indicating that at least twenty-four people on the ground were killed and many more injured.&nbsp;&nbsp;</p><p dir="ltr" style="text-align: justify;">Video of the takeoff and flight prior to the crash shows that the aircraft impacted the medical hostel approximately one mile from the runway.&nbsp; The video also shows that the aircraft struggled to gain altitude after takeoff likely due to a power failure.&nbsp; Immediately upon takeoff the flight crew contacted air traffic control and advised “mayday . . . no thrust, losing power, unable to lift” but no further communications were heard from the pilots.&nbsp;&nbsp;</p><p dir="ltr" style="text-align: justify;">Indian aviation accident investigators will be joined by experts from the United States National Transportation Safety Board (“NTSB”) and the United Kingdom Air Accidents Investigation Branch (“AAIB”) to investigate the crash. Representatives from Boeing, the aircraft manufacturer, and GE Aerospace, the engine manufacturer, will also participate in the accident investigation and provide technical assistance.&nbsp; Critical to the investigation will be the data captured by the “black boxes”, the Cockpit Voice Recorder and the Digital Flight Data Recorder. These are sophisticated recording devices that capture a large amount of information.&nbsp; This analysis will provide significant detail into what the flight crew and the aircraft were doing during the short flight prior to the crash, and it has been reported that the Digital Flight Data Recorder has been recovered.&nbsp;&nbsp;&nbsp;</p><p dir="ltr" style="text-align: justify;">Speiser Krause has decades of experience in handling international aviation disasters, including cases against Boeing dating back to the 1960s, and has litigated these cases throughout the world. The Firm will closely monitor developments in the accident investigation.&nbsp;</p><span><br></span>]]></description><pubDate>Mon, 16 Jun 2025 11:05:00 GMT</pubDate><category>Blogs</category></item><item><title><![CDATA[Speiser Krause Monitoring the Crash of a Mitsubishi MU-2B-40 Aircraft in Copake, New York]]></title><link>https://speiserkrause.com/lawyer/2025/05/08/News/Speiser-Krause-Monitoring-the-Crash-of-a-Mitsubishi-MU-2B-40-Aircraft-in-Copake,-New-York_bl54308.htm</link><description><![CDATA[<p>On Saturday, April 12, 2025, at approximately 12:06 p.m., a Mitsubishi MU-2B-40 Solitaire aircraft, bearing Federal Aviation Administration Number N635TA, crashed in upstate New York 10 miles from the Columbia Airport.&nbsp; The crash tragically killed all six occupants.&nbsp; The aircraft was traveling to upstate New York for a family gathering as well as to celebrate the Passover Holiday.&nbsp; On board were physicians, who were spouses, with the husband as the pilot.&nbsp; Also on board were two adult children of the couple, as well as their partners.&nbsp; A third child of the physician-couple was not on board.&nbsp; The aircraft was owned by Dynamic Spine Solutions LLC, a limited liability company registered in Massachusetts. </p><p>The pilot had attempted to land at the Columbia County Airport when he contacted Air Traffic Control and advised that he executed a missed approach to the airport.&nbsp; Instead of following published missed approach procedures the pilot requested vectors for another approach to landing.&nbsp; During the second approach, the air traffic controller who was in communication with the aircraft received a “LA” or Low Altitude Alert on the radar display that he was using.&nbsp; He attempted to contact the aircraft on several occasions but he did not receive a response nor was there a distress call from the aircraft prior to the crash. &nbsp;</p><p>The National Transportation Safety Board (“NTSB”) launched a “Go Team” to the crash site and it is the lead federal agency investigating the crash.&nbsp; The NTSB assigned various entities to assist in its investigation, including, Mitsubishi (the manufacturer of the aircraft); Honeywell (the engine manufacturer); the Federal Aviation Administration; and NATCA (the union representing air traffic controllers).</p><p>Although manufactured in 1985, the aircraft was purchased approximately one year ago, and it was equipped with an advanced and upgraded avionics package.&nbsp; The aircraft was also equipped with advanced cockpit technology, including a memory card that the NTSB will analyze which will hopefully provide additional information concerning the crash. </p><p>With respect to its preliminary investigation, the NTSB confirmed that shortly before the crash, the aircraft was operating under Instrument Flight Rules (“IFR”), that the weather conditions were deteriorating, and snow was visible on the ground.&nbsp; The NTSB also advised that it is in possession of a video that shows the impact of the aircraft with the ground, that the crash occurred at a high rate of descent, and that it appeared that the aircraft had not suffered a structural failure prior to the crash.&nbsp; Weather, including if ice had accumulated on the aircraft structure, will be a part of the NTSB’s accident investigation.</p><p>The Mitsubishi MU-2B-40 model aircraft is a high wing high-powered twin turbo engine aircraft and it has had a significant safety history.&nbsp; Given the challenging nature of piloting the aircraft, the FAA requires that pilots receive specific training particular to this model aircraft, including annual recurrent training on special emphasis items. In a press conference the NTSB advised that the pilot had undergone the additional required training.&nbsp; While it is far too early to speculate, the model of the accident aircraft is susceptible to icing – specifically tail icing – which could result in a loss of control.&nbsp; When ice accretes on an aircraft’s airframe this could result in the disruption of airflow over the tail and wings which could cause a loss of control.&nbsp;&nbsp;&nbsp;&nbsp; </p><p>The NTSB advised that it hopes to release its Preliminary Report within thirty days of the crash.&nbsp; Speiser Krause will provide additional details as more information is released.&nbsp; &nbsp;<br><br></p>]]></description><pubDate>Thu, 08 May 2025 09:11:00 GMT</pubDate><category>Blogs</category></item><item><title><![CDATA[Speiser Krause Retained in the Mid-Air Collision over the Potomac River]]></title><link>https://speiserkrause.com/lawyer/2025/02/04/News/Speiser-Krause-Retained-in-the-Mid-Air-Collision-over-the-Potomac-River_bl54264.htm</link><description><![CDATA[<p>The team at Speiser Krause extends its sympathy to those tragically impacted by the recent mid-air collision.  The families of the victims are first and foremost in our hearts and minds and we are here to help navigate the difficult days ahead. </p>

<p>On Wednesday, January 29, 2025, American Eagle Flight 5342 (a CRJ700 aircraft) operated by PSA Airlines was seconds away from landing at Ronald Reagan Washington National Airport and was established on short final for its landing on Runway 33. At approximately 350 feet above the Potomac River the CRJ700 and a U.S. Army Sikorsky UH-60 Black Hawk helicopter operating on a training flight collided at approximately 8:48 p.m. Tragically, all 60 passengers and 4 flight crew members on the American Eagle Flight were killed, as were 3 U.S. Army personnel in the Black Hawk helicopter.</p>

<p>A depiction of the collision is set forth below:
<img src="/global_pictures/sk-map.jpg"></p>

<p>During its approach to the airport, the American Eagle flight accepted an offer from air traffic control (“ATC”) to land on Runway 33 which is significantly shorter than Runway 1 at Reagan National.</p>

<p>The airport, which lies on the Virginia side of the Potomac River, is extremely busy and the airspace around the airport is heavily congested.  Extreme vigilance is always required when operating in any aircraft environment but more so here, given the nature of the airspace and the amount of air traffic utilizing the airport.</p>

<p>The accident investigation is being led by the National Transportation Safety Board (“NTSB”) and the U.S. Army will also be heavily involved.  The investigation will likely take more than  a year to complete.  However, preliminary information indicates that both the American Eagle Flight and the Black Hawk helicopter were in communication with ATC at Reagan National.  The helicopter was transiting the area flying on what is known as a low-level helicopter route over the Potomac River.  ATC apparently saw that the two aircraft were on a possible collision course and instructed the Black Hawk helicopter to fly behind the American Eagle flight, which the helicopter acknowledged.  It is unknown if the helicopter pilot mistook another aircraft for American Eagle Flight 5342 but this is something that will be examined during the accident investigation, and it is anticipated that a visibility study will be conducted to determine what each pilot may have seen. Investigators will also look at whether the Black Hawk helicopter was operating above its permissible altitude at the time of the crash.</p>

<p>While monitoring the government’s accident investigation, the team at Speiser Krause is also analyzing the information being released as well as conferring with experts to determine possible causes of this unspeakable tragedy.  The lawyers at Speiser Krause have extensive experience involving mid-air collisions, including above navigable waters, having represented passengers who were killed due to a mid-air collision over the Hudson River in 2009 between a fixed wing aircraft and a helicopter, and recently, those injured as a result of a mid-air collision in 2019 between two sight seeing aircraft over the George Inlet, Alaska.  
Our firm is dedicated to representing the victims of aviation tragedies and we do all that we can to ensure that a tragedy like this never happens again.  We will look at all circumstances surrounding the flight including the conduct of the pilots and ATC.
Cases involving ATC and potential U.S. Army negligence involve specialized laws including, but not limited to, the Federal Tort Claims Act (“FTCA”), aviation statutes and regulations including the Federal Aviation Act, as well as the policies and procedures governing the conduct of air traffic control.  Not only has the team at Speiser Krause been involved with numerous actions involving mid-air collisions but we have litigated dozens of lawsuits against ATC.  </p>

<p>We will continue to provide additional updates as more information becomes available.</p>]]></description><pubDate>Tue, 04 Feb 2025 12:37:00 GMT</pubDate><category>Blogs</category></item><item><title><![CDATA[Speiser Krause Monitoring the MedeVac Crash in Philadelphia, Pennsylvania on Friday, January 31, 2025]]></title><link>https://speiserkrause.com/lawyer/2025/02/03/Recent-Developments/Speiser-Krause-Monitoring-the-MedeVac-Crash-in-Philadelphia,-Pennsylvania-on-Friday,-January-31,-2025_bl54265.htm</link><description><![CDATA[<p>Less than one-minute after takeoff on the evening of January 31, 2025, a Learjet 55 model aircraft owned by Jet Rescue Air Ambulance, a Mexican based operator, crashed into a busy Philadelphia neighborhood killing all six occupants on board as well as an individual on the ground. Twenty-four other individuals on the ground were injured, some critically.  The primary debris field spans 4-6 blocks and additional debris has been located throughout the Philadelphia neighborhood.  The aircraft had departed from the Northeast Philadelphia Airport with an intended stop at the Springfield-Branson National Airport in Missouri before proceeding to its destination in Tijuana, Mexico.  All six persons aboard the aircraft were Mexican Nationals, including a pediatric patient who had received life-saving medical care in Philadelphia.  The patient’s mother also died in the crash, as did a physician, paramedic and the two-person flight crew.
Video of the crash showed the accident aircraft in a severe nose down pitch attitude and impacted the ground with significant force causing a crater and massive fireball.  The crash caused substantial property damage including engulfing in fire five homes and numerous vehicles.  </p>
<p>The National Transportation Safety Board is leading the investigation into this deadly crash.  The NTSB located the aircraft’s Cockpit Voice Recorder in a crater 8 feet deep.  Investigators also recovered the aircraft’s Enhanced Ground Proximity Warning System (EGPWS) which should contain flight data including data from the accident flight.  The NTSB’s Vehicle Recorder Division and Laboratory will analyze both the CVR and EGPWS and it is expected that these components will assist investigators in determining the cause of his tragedy.  
Speiser Krause, a national aviation law firm with offices in Huntingdon Valley, Pennsylvania, will continue to provide updates as more information is released.</p>]]></description><pubDate>Mon, 03 Feb 2025 10:11:00 GMT</pubDate><category>Blogs</category></item><item><title><![CDATA[Speiser Krause Monitoring Investigation Into Crash of HondaJet that Occurred in Mesa, Arizona on Tuesday, November 5, 2024]]></title><link>https://speiserkrause.com/lawyer/2024/11/13/News/Speiser-Krause-Monitoring-Investigation-Into-Crash-of-HondaJet-that-Occurred-in-Mesa,-Arizona-on-Tuesday,-November-5,-2024_bl54222.htm</link><description><![CDATA[<p>On Tuesday November 5, 2024, a HondaJet Model HA-420 bearing Federal Aviation Registration Number N57HP which was owned by Ice Man Holdings LLC crashed due to an attempted aborted takeoff from Falcon Field (KFFZ) in Mesa, Arizona.  The aircraft departed the end of the runway, crashed through a perimeter fence and hit an automobile as it was travelling on North Greenfield Road.  Tragically, four occupants of the aircraft and the driver of the vehicle perished as a result.  One aircraft occupant sustained severe personal injuries.</p>

<p>At approximately 4:40 p.m. the aircraft commenced its takeoff roll for its intended flight from Falcon Field to Provo Municipal Airport in Provo, Utah.  The aircraft received its takeoff clearance from Runway 22L which the pilot acknowledged.  There were no further communications with air traffic control. </p>

<p>According to ADS-B data, the aircraft accelerated to approximately 133 knots ground speed on the 5,100-foot-long asphalt runway.  Pursuant to published data, the decision speed, known as V1, is approximately 110 knots which means that if a takeoff is rejected when the aircraft is travelling more than 110 knots it will be unable to stop on the remaining runway.  Here, for reasons that are yet to be determined, the aircraft was unable to gain lift and commenced RTO (Rejected Takeoff) Procedures.  Unfortunately, and since the aircraft’s ground speed exceeded the takeoff decision speed, or V1, at the time of the attempted rejected takeoff it was unable to stop on the remaining runway, and it then crashed through a perimeter fence and came to rest after colliding with the vehicle on North Greenfield Road.  A post-crash fire ensued.</p>

<p>The HondaJet is marketed as a light business jet and is manufactured by the Honda Aircraft Company in Greensboro, North Carolina.  Speiser Krause has successfully represented both flight crew and passengers in runway excursions on takeoff.  The Firm recently represented the co-pilot of a Cessna Citation Jet who was tragically killed in a failed takeoff which was caused by an inadvertently set parking brake.  In the Cessna accident, the jet departed the end of the runway, then gained lift but stalled crashing into a pole and nearby warehouse.  All four aircraft occupants were killed in that crash.</p>

<p>The National Transportation Safety Board (“NTSB”) is the lead federal agency responsible for the accident investigation. The NTSB will examine a host of issues including the aircraft, environmental conditions and pilot actions.  It is anticipated that the NTSB will focus on why the aircraft could not rotate (or lift off the runway) despite sufficient ground speed.</p>

<p>A Preliminary Report should be issued by the NTSB within the coming weeks, but the Factual Report detailing the NTSB’s investigative activities will likely take a year or more.
</p>]]></description><pubDate>Wed, 13 Nov 2024 13:00:00 GMT</pubDate><category>Blogs</category></item><item><title><![CDATA[Update Regarding Crash of de Havilland DHC-2 Beaver in Ontario, Canada]]></title><link>https://speiserkrause.com/lawyer/2024/09/20/Recent-Developments/Update-Regarding-Crash-of-de-Havilland-DHC-2-Beaver-in-Ontario,-Canada_bl54184.htm</link><description><![CDATA[<p>Speiser Krause has been retained by all passengers involved in connection with the crash of a de Havilland DHC-2 Beaver floatplane that occurred on June 16, 2024, in the Chukuni River, Ontario.  The passengers, all US citizens, were on a fishing trip and were travelling to a remote location in Ontario.  The crash occurred on takeoff when the pilot lost control and crashed into the shoreline.  One passenger tragically succumbed to his injuries and three other passengers suffered serious injuries.  The crash is being investigated by the Transportation Safety Board of Canada which is similar to the National Transportation Safety Board in the United States.</p>]]></description><pubDate>Fri, 20 Sep 2024 09:24:00 GMT</pubDate><category>Blogs</category></item><item><title><![CDATA[Crash of de Havilland DHC-2 Beaver in Ontario, Canada]]></title><link>https://speiserkrause.com/lawyer/2024/06/26/News/Crash-of-de-Havilland-DHC-2-Beaver-in-Ontario,-Canada_bl54143.htm</link><description><![CDATA[<p>Speiser Krause is investigating the crash of a de Havilland DHC-2 Beaver aircraft that crashed during an attempted takeoff in the early morning of June 16, 2024.&nbsp; The four passengers were set to enjoy a fly-fishing trip when they were being transported from the Operator’s base in Ontario, Canada to a remote lake.&nbsp; Two of the passengers were seriously injured, one of whom tragically passed away in the hospital days after the crash.&nbsp; It has been reported that the two other passengers and the pilot were treated for minor injuries.</p><p>Speiser Krause has extensive experience involving de Havilland DHC-2 Beaver and DHC-3 Otter aircraft, recently concluding litigation involving a midair collision in Alaska involving these types of aircraft.&nbsp; Speiser Krause has also litigated numerous crashes in Canada recently resolving litigation involving the crash of a Kaman K-1200 helicopter that crashed during heli-logging operations in British Columbia, Canada, in which the pilot was killed.
</p><p>
The Transportation Safety Board of Canada (similar to the National Transportation Safety Board) has sent two investigators to the crash scene to gather evidence and assess the causal factors in the crash.&nbsp; Partners Douglas A. Latto and Jeanne M. O’Grady are monitoring the accident investigation.</p>]]></description><pubDate>Wed, 26 Jun 2024 16:56:00 GMT</pubDate><category>Blogs</category></item></channel></rss>