Piper PA-28-140 accident near Phoenix, Arizona, March 4, 2026
On March 4, 2026 at about 2:21 pm local time, a 1968 Piper PA-28-140, registered N7744T, was substantially damaged in an accident during initial climb near Phoenix, Arizona (Phoenix Deer Valley Airport). It was an instructional flight under general aviation rules (Part 91). 1 person was seriously injured and 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 4, 2026 · about 2:21 pm local time
- Place
- Phoenix, Arizona · Phoenix Deer Valley Airport · map
- Type
- Accident
- Injuries
- 1 person was seriously injured and 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-28-140, built 1968 · all PA-28-140s on the register
- Registration
- N7744T · registry record · serial 28-24073
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
On March 4, 2026, about 0721 mountain standard time, a Piper PA-28-140, N7744T, was substantially damaged when it was involved in an accident near Phoenix, Arizona. The flight instructor was seriously injured, and the student pilot and one person on the ground sustained minor injuries. The airplane was operating as a Title 14 Code of Federal Regulations Part 91 instructional flight. Preliminary ADS-B data provided by the Federal Aviation Administration (FAA) indicated that the airplane departed from runway 07R at Phoenix Deer Valley Airport (DVT), Phoenix, Arizona, about 0715, and continued on the upwind leg for about 1.5 miles before making a slight left turn toward the northeast. According to the student pilot, the flight was destined for the northeast practice area. About 0719, at an altitude of about 1,700 ft above ground level, ADS-B data showed that the airplane initiated a left turn to the west in the direction of DVT. The airplane subsequently entered a gradual descent and continued a southwestern track toward DVT for about 2.8 miles. According to the flight instructor, after the onset of engine power loss, he made a radio call to the DVT tower to advise them of the situation and his intention to return to the airport. He reported that the engine rpm decreased to about 600–700 rpm, accompanied by rough vibrations. He applied full throttle and leaned the mixture, which resulted in a slight increase in engine rpm. He then configured the airplane for best glide speed while continuing toward DVT. The flight instructor stated that during the return flight, the engine continued to produce reduced power. About 5 to 10 seconds before impact, the engine lost power completely. A review of video footage from a nearby residential home security camera captured the airplane approaching the accident site at a low altitude. The airplane subsequently entered a shallow right turn, followed by an increase in pitch, after which the right wing dropped. The airplane impacted the roof of a residence and subsequently struck an exterior wall of an adjacent second residence, before it came to rest in the second home's backyard. Examination of the accident site revealed that the airplane impacted a residential neighborhood about 2 miles northeast of DVT. The fuselage, along with the left wing, came to rest on the ground at the base of a house in a near-vertical, nose-down attitude on a magnetic heading of approximately 052°. The right wing was separated and remained lodged within the roof of the first residence. Wreckage debris remained within about 20 ft of the wreckage, which included the right-wing flap, the nose landing gear, as well as fragments of fuselage skin. The engine and propeller assembly remained attached to the airframe and was compressed upward and to the right. The wreckage was recovered to a secure location for further examination.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of engine power (partial) during initial climb defining event
- Loss of engine power (total) during emergency descent
- Aerodynamic stall/spin during emergency descent
The aircraft
- Airframe total time: 5,929.6 hours
- Last inspection: annual inspection, June 2, 2025; 91.2 hours since
- Maximum gross weight: 2,150 lb
- Seats: 4
- Landing gear: fixed
The flight
- Flight plan: none
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 050° at 3 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 55°F (13°C), dew point 28°F (-2°C)
- Altimeter: 29.96 inHg
- Observation at 7:00 am from KDVT, 1 miles away
Weather report (METAR): METAR KDVT 041353Z 05003KT 10SM CLR 13/M02 A2996 RMK AO2 SLP131 T01281017
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
