Regulations & Safety
Piper PA-28 Crashes in North Phoenix Neighborhood Injuring Three
A small plane crashed near Deer Valley Airport in North Phoenix, injuring three and damaging two homes. FAA and NTSB investigate the incident.
This article summarizes reporting by 12News and journalist Adam Correa.
A single-engine aircraft crashed into a residential neighborhood in North Phoenix on the morning of Wednesday, March 4, 2026, injuring three people and damaging two homes. According to reporting by 12News, the incident occurred near the intersection of Deer Valley and Cave Creek roads as the plane attempted to return to the nearby airport.
Emergency responders arrived at the scene in the 2000 block of East Parkside Lane shortly after 7:30 a.m. MST. The aircraft, identified by authorities as a Piper PA-28, struck the roof of one residence before coming to rest in the backyard of a neighboring property. While the crash caused significant structural damage and a fuel leak, officials have confirmed there were no fatalities.
The crash occurred during the morning rush hour, a time when many residents were still at home. Preliminary information cited by local outlets indicates that the aircraft had recently departed from Deer Valley Airport (DVT), one of the busiest general aviation airports in the world.
According to the Federal Aviation Administration (FAA), the pilot appeared to be attempting a return to the airfield shortly after takeoff. While the National Transportation Safety Board (NTSB) has not yet determined a probable cause, an immediate return to the airport often suggests a mechanical anomaly or onboard emergency. The Piper PA-28 is a common trainer aircraft, and reports confirm that a flight instructor and a student pilot were the two occupants on board.
The Phoenix Fire Department responded rapidly to the scene to manage potential fire hazards and treat the victims. Three individuals were transported to local hospitals.
Both the flight instructor and the student pilot survived the impact. They were transported in stable condition with injuries described by responders as cuts and burns. On the ground, one resident, a homeowner, was also injured. Reports suggest the resident was either inside the home or in the backyard at the moment of impact; they were hospitalized as a precaution.
The collision caused distinct damage to two separate properties. The plane clipped the roof line of the first home before crashing into the second home’s yard. The impact ruptured the aircraft’s fuel tanks, causing fuel to leak into the attic of one of the structures. Hazmat crews were deployed to contain the spill and prevent environmental contamination or fire. “Situations like this when you do have multiple residences involved… it is a miracle that no one was [seriously] injured.”
— Phoenix Fire Department spokesperson
Federal investigators from the NTSB and FAA are currently on-site to document the wreckage and determine the sequence of events leading to the crash. The investigation will likely focus on engine performance, pilot communications with air traffic control, and weather conditions at the time of the flight.
Deer Valley Airport handles over 400,000 flight movements annually, heavily driven by flight training operations. The surrounding area is densely populated, creating a complex interface between urban residential zones and aviation activities. While crashes in these neighborhoods are statistically rare given the volume of traffic, this incident follows a pattern of occasional emergency landings in the open lots and streets surrounding the airport.
Training density and urban planning: The survival of all involved in this crash highlights the crashworthiness of modern general aviation airframes, but it also underscores the risks inherent in the “urban interface” of busy training airports. Deer Valley Airport was once surrounded by open desert, but Phoenix’s rapid northward expansion has encircled the facility with residential housing.
When training aircraft suffer power loss on takeoff, the most critical phase of flight, pilots have very few options if they cannot glide back to the runway. In this instance, the pilot’s attempt to turn back, a maneuver known to be high-risk at low altitudes, suggests the situation was critical. The lack of fatalities is indeed fortunate, but this event will likely renew local discussions regarding flight path zoning and safety buffers in North Phoenix.
Small Plane Crashes into North Phoenix Neighborhood; Three Injured
Incident Timeline and Flight Details
Attempted Return to Airport
Injuries and Property Damage
Occupants and Residents
Structural Impact and Hazmat Response
Investigation and Safety Context
Deer Valley Airport Operations
AirPro News Analysis
Sources
Photo Credit: X
Regulations & Safety
Singapore Airlines A350 Collides with Spirit Airlines Jet at Newark Airport
A Singapore Airlines A350 clipped a parked Spirit Airlines jet during pushback at Newark Airport. Singapore flight continued; Spirit flight was cancelled.
This article summarizes reporting by ABC7NY and aviation data reports.
A Singapore Airlines Airbus A350-900 preparing for the world’s longest commercial flight collided with a parked Spirit Airlines aircraft at Newark Liberty International Airport (EWR) on the morning of March 3, 2026. The incident, which occurred during pushback near Terminal B, resulted in damage to both aircraft but caused no injuries to passengers or crew.
According to reporting by ABC7NY, the collision took place as the Singapore Airlines jet was maneuvering away from the gate. Its right wingtip made contact with the tail of a stationary Spirit Airlines plane. While the Spirit flight was subsequently cancelled due to the damage, the Singapore Airlines aircraft was inspected and eventually cleared to continue its journey.
The collision occurred at approximately 10:20 AM EST. Aviation data indicates that the Singapore Airlines aircraft, operating as Flight SQ21, was pushing back for its scheduled departure to Singapore (SIN). The Spirit Airlines aircraft, an Airbus A321neo operating as Flight NK992 to Orlando (MCO), was parked and undergoing de-icing at the time of impact.
Audio recordings from LiveATC captured the immediate reaction from the cockpit of the Singapore Airlines jet. The pilot reported the incident to the tower shortly after the impact.
“Uh, right wing may have touched the Spirit behind us.”
, Pilot audio via LiveATC
Following the collision, the Singapore Airlines crew requested a tow back to the gate to assess the situation. Emergency services and ground crews responded to the scene at Terminal B, an area of the airport typically controlled by airline ramp personnel rather than Air Traffic Control.
The Singapore Airlines aircraft involved was identified as an Airbus A350-900, registration 9V-SGA. This specific aircraft is configured for the carrier’s ultra-long-range missions. Flight SQ21 covers approximately 9,500 miles and can take up to 19 hours. Despite the collision, engineers inspected the wing structure and deemed the aircraft safe for flight. It departed later in the day to complete its journey to Singapore. The Spirit Airlines aircraft, identified as N720NK, sustained damage to its tail section. Unlike the Singapore Airlines flight, the Spirit flight was unable to proceed. The flight was cancelled, and passengers were deplaned and rebooked on alternate flights to Orlando.
The Federal Aviation Administration (FAA) has confirmed it is investigating the incident. In a statement referenced by reports, the agency noted that the collision occurred in a “non-movement area,” referring to the ramp sections where aircraft are guided by wing walkers and tug drivers rather than direct tower control.
Spirit Airlines confirmed that their aircraft was stationary during the event. “Our aircraft was parked and undergoing de-icing when the wing clip occurred,” the airline stated, emphasizing that their priority was re-accommodating affected guests.
Singapore Airlines acknowledged the incident, stating that their engineering team carried out a full inspection of the Airbus A350-900 before clearing it for departure.
Ramp Congestion at Newark
Newark Liberty International Airport is notorious for its tight ramp areas and high congestion, particularly during peak morning departure banks. “Wing clip” incidents, while minor in terms of passenger safety, highlight the precision required during pushback operations. In confined spaces like the Terminal B ramp, the margin for error is slim. The fact that the Spirit aircraft was undergoing de-icing adds another layer of complexity to the ground environment, as de-icing trucks and personnel reduce the available maneuvering space for passing aircraft.
While the damage to the Singapore Airlines jet was evidently superficial enough to allow it to fly a 19-hour transpacific route, the grounding of the Spirit jet suggests the tail section took the brunt of the force. Structural repairs to the tail of an A321neo can be costly and time-consuming, potentially removing the airframe from service for several days or weeks.
Was anyone injured in the collision? Did the Singapore Airlines flight cancel? What caused the collision?
Singapore Airlines A350 Clips Spirit Airlines Jet at Newark Liberty International Airport
Incident Details and Timeline
Aircraft and Operational Impact
Flight SQ21: The World’s Longest Flight
Spirit Airlines Flight NK992
Official Statements and Investigation
AirPro News Analysis
Frequently Asked Questions
No. There were no reported injuries among the passengers or crew on either the Singapore Airlines or Spirit Airlines aircraft.
No. Although it was delayed for inspection, Flight SQ21 was cleared by engineers and departed for Singapore later the same day.
The incident occurred during pushback. While an official cause has not been determined by the FAA investigation, these incidents are typically attributed to misjudgments regarding clearance between wingtips and obstacles in tight ramp areas.
Sources
Photo Credit: X
Regulations & Safety
Two Survive Engine Failure Crash in Hudson River Near Newburgh
A Cessna 172 ditched into the Hudson River near Newburgh after engine failure. Both occupants survived with minor injuries and are under investigation.
This article summarizes reporting by NBC New York and The Associated Press.
In a striking parallel to the famous 2009 emergency landing by Captain Chesley “Sully” Sullenberger, a small aircraft successfully ditched into the Hudson River on Monday night, resulting in the survival of both occupants. According to reporting by NBC New York and The Associated Press, the single-engine Cessna 172 crashed into the frigid waters near the Newburgh-Beacon Bridge, approximately 60 miles north of Manhattan.
Officials have described the event as a “mini Miracle on the Hudson,” noting the remarkable escape of the pilot and passenger. Despite air temperatures hovering around 27°F and water temperatures estimated between 36°F and 39°F, both individuals managed to exit the sinking aircraft and swim approximately 200 feet to the shoreline. They were subsequently treated for minor injuries at St. Luke’s Cornwall Hospital.
The incident occurred at approximately 7:55 PM ET on Monday, March 2, 2026. The aircraft, identified as a Cessna 172 Skyhawk (Registration N1560E) operated by American Airman Inc., had departed from Long Island MacArthur Airport earlier that evening. Flight tracking data indicates the plane circled near Stewart International Airport before heading south and eventually turning back north near West Point.
According to preliminary information cited by local authorities, the pilot declared an emergency due to engine failure. Unable to reach a runway, the pilot executed a controlled ditching into the river. Witness Brendan Gallagher, a fellow pilot flying overhead, described the tense moments to reporters.
“We saw they were going down in the river… Thank God they landed upright.”
, Brendan Gallagher, witness pilot (via NBC New York)
The survival of the occupants is being hailed as a physiological feat given the environmental conditions. With water temperatures near freezing, the risk of cold water shock was immediate. However, first responders from the Middle Hope Fire Department and other agencies arrived to find the victims had already reached the shore near 401 Water Street in Newburgh.
Government officials quickly drew comparisons to the 2009 “Miracle on the Hudson,” where US Airways Flight 1549 landed safely in the river with 155 people on board. While this week’s crash involved a much smaller general aviation aircraft, the outcome was similarly fortunate. New York Governor Kathy Hochul took to social media to praise the outcome, calling it “Another miracle on the Hudson.” Orange County Executive Steve Neuhaus also emphasized the rarity of the survival.
“[It is] Miracle on the Hudson Part Two.”
, Steve Neuhaus, Orange County Executive
The aircraft itself is unlikely to be recovered intact. The plane was reported to be drifting under ice blocks following the crash. Executive Neuhaus noted the grim reality of the airframe’s future in a statement to the press.
“[The aircraft is] presently on its way to becoming an artificial reef.”
, Steve Neuhaus (via NBC New York)
The Federal Aviation Administration (FAA) and the National Transportation Safety Board (NTSB) have launched investigations to determine the precise cause of the engine failure. Recovery of the wreckage will be a critical component of this inquiry, though river conditions may complicate salvage operations.
While the “Miracle” comparison is apt regarding the survival rate, the dynamics of this crash differ significantly from the 2009 event. A Cessna 172 has a much lower approach speed than an Airbus A320, which likely contributed to the survivability of the impact. However, the decision to ditch at night in icy conditions presents a higher degree of difficulty regarding visibility and immediate hypothermia risks. The successful self-rescue, swimming 200 feet in 36°F water, suggests the occupants were not only lucky but physically resilient, as incapacitation from cold water usually sets in within minutes.
“Mini Miracle” on the Hudson: Two Survive Icy Plane Crash Near Newburgh
Emergency Landing and Survival
Engine Failure and Ditching
The Swim to Safety
Official Response and Investigation
Status of the Wreckage
AirPro News Analysis
Frequently Asked Questions
Sources
Photo Credit: X
Regulations & Safety
NTSB Report Details Altitude Deviation in Epic E1000 Crash
NTSB preliminary report finds Epic E1000 turboprop descended below minimum altitude before fatal crash near Steamboat Springs, Colorado.
This article is based on the preliminary investigation report released by the National Transportation Safety Board (NTSB) regarding the incident involving N98FK.
The National Transportation Safety Board (NTSB) has released its preliminary report regarding the fatal crash of an Epic E1000 turboprop near Steamboat Springs, Colorado. The accident, which occurred on February 13, 2026, claimed the lives of the pilot and three passengers. The investigation’s initial findings suggest the aircraft was flying a stable descent profile but was operating below the required minimum altitude for that segment of the approach prior to impacting terrain.
This incident marks a significant event in general aviation as it appears to be the first fatal hull loss involving the certified production model of the Epic E1000. Previous accidents involving this airframe type were limited to the experimental “LT” kit-built versions. While the preliminary report offers factual data gathered shortly after the accident, it does not yet determine a probable cause, a conclusion that typically requires 12 to 24 months of analysis.
According to the NTSB, the flight originated in Nashville, Tennessee, and made a scheduled fuel stop at Kansas City Charles B. Wheeler Downtown Airport (KMKC) before departing for Bob Adams Airport (KSBS) in Steamboat Springs. The aircraft, registered as N98FK, was conducting an Instrument Flight Rules (IFR) approach to Runway 32 shortly after midnight local time.
Flight track data recovered by investigators indicates that the aircraft was established on the RNAV (GPS)-Z approach. However, the data reveals a critical deviation from the published approach procedures. The report notes that the aircraft crossed the waypoint WDCHK at approximately 9,025 feet Mean Sea Level (MSL).
For this specific segment of the approach, the published Minimum Descent Altitude (MDA) is 9,100 feet MSL. The aircraft was roughly 75 feet below the required floor for that sector. The descent rate was recorded as steady, approximately 1,000 feet per minute, with no sudden maneuvers or distress calls transmitted by the pilot, suggesting a controlled flight profile up until the moment of impact.
The aircraft impacted the south-facing slope of Emerald Mountain (also known locally as Quarry Mountain) at an elevation of approximately 8,250 feet MSL. The mountain, located about three nautical miles south of the destination airport, has a summit elevation between 8,200 and 8,300 feet. The impact point suggests the aircraft did not level off at the required altitude to clear the terrain obstacles in the final approach path.
The investigation has highlighted several environmental and infrastructural factors that may have complicated the night approach into the mountainous region. At the time of the accident, Notices to Air Missions (NOTAMs) indicated that critical visual landing aids for Runway 32 were out of service. Specifically, the Runway End Identifier Lights (REILs) and the Precision Approach Path Indicator (PAPI) were inoperative. The PAPI system is particularly vital for night operations in mountainous terrain, as it provides pilots with visual vertical guidance to ensure they remain on a safe glide path clear of obstacles.
Meteorological reports from the time of the crash indicate that conditions were technically Visual Flight Rules (VFR), though visibility was variable due to cloud layers. Visibility was reported between 5 and 10 statute miles. The NTSB noted scattered clouds at 500 feet Above Ground Level (AGL), broken layers between 2,400 and 2,600 feet AGL, and an overcast layer at 4,100 feet AGL. Winds were reported as light and variable.
The aircraft involved was a 2024 model Epic E1000, a high-performance single-engine turboprop powered by a Pratt & Whitney PT6A-67A engine. It was equipped with the Garmin G1000 NXi avionics suite, a modern system that typically includes synthetic vision and terrain awareness capabilities.
Local authorities in Routt County identified the four victims as residents of the Franklin, Tennessee area. They included the pilot and owner, Aaron Stokes (47), his son Jakson Stokes (21), his nephew Colin Stokes (21), and family friend Austin Huskey (37). There were no survivors.
The Risks of Night Approaches in Mountainous Terrain
While the NTSB has not yet assigned cause, the factual evidence presented in the preliminary report aligns with the profile of a Controlled Flight Into Terrain (CFIT) event. In CFIT accidents, a mechanically sound aircraft is flown inadvertently into the ground, often due to a loss of situational awareness.
The absence of the PAPI system is a critical detail. Without visual vertical guidance, pilots flying at night into “black hole” conditions, where few ground lights exist to provide depth perception, must rely strictly on their altimeters and approach charts. The “step-down” nature of the approach into Steamboat Springs requires precise adherence to altitude floors at specific waypoints. The data showing the aircraft below the MDA at the WDCHK waypoint suggests a possible premature descent or a failure to level off, a common precursor to CFIT in complex terrain.
What is a Preliminary Report? When will the final report be released? Was the aircraft equipped with terrain warning systems?
NTSB Preliminary Report Reveals Altitude Deviation in Fatal Epic E1000 Crash
Flight Trajectory and Impact Details
Altitude Discrepancies
Collision with Terrain
Operational Environment and Infrastructure
Compromised Visual Aids
Weather Conditions
Aircraft and Victim Identification
AirPro News Analysis
Frequently Asked Questions
A preliminary report is an initial release of factual information gathered by the NTSB shortly after an accident. It details the “what” and “where” but does not analyze the “why.” It does not determine probable cause.
The NTSB typically takes between 12 and 24 months to complete a full investigation and issue a final report with a probable cause determination.
Yes, the Epic E1000 is equipped with the Garmin G1000 NXi suite, which includes terrain awareness features. Investigators will likely analyze why these systems did not prevent the collision, or if the warnings were not perceived.
Sources
Photo Credit: Aviation Safety Network
-
Regulations & Safety3 days agoFAA Revokes Starflite Aviation Certificate Over Falsified Records
-
Regulations & Safety1 day agoSingapore Airlines A350 Collides with Spirit Airlines Jet at Newark Airport
-
Business Aviation3 days agoMexico’s Updated APIS Protocols and Doors Closed Confirmation
-
Technology & Innovation23 hours agoRTX Hybrid-Electric Plane Demonstrator Completes Key Ground Test
-
Defense & Military4 days agoLockheed Martin Launches Dominance in the Skies Campaign with Vectis Drone
