Tuesday, September 08, 2026

Cessna 172N Skyhawk II, N734ZK, fatal accident occurred on September 7, 2026, at Montgomery-Gibbs Executive Airport (MYF/KMYF), San Diego, California

This is preliminary information, subject to change, and may contain errors. Any errors in this writing will be corrected when/if the NTSB preliminary report is released.

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N734ZK

- History of Flight:
On September 7, 2026, at about 1719 local time, a privately-registered Cessna 172 Skyhawk II, N734ZK, was destroyed when it was involved in an accident at Montgomery-Gibbs Executive Airport (MYF/KMYF), San Diego, California. The 
flight instructor and student pilot were fatally injured. The local training flight originated from KMYF.

According to flight-tracking history, the airplane was a frequent flyer out of KMYF, flying out on local flights on daily bases.

According to Automatic dependent surveillance-broadcast (ADS-B) data, at 1156 local time, the airplane departed KMYF and headed north to conduct a number of maneuvers before returning to the airport. The airplane conducted two touch-and-go(es) on runway 28L before coming to a stop. The flight lasted 49m.

At 1627, the airplane departed KMYF again and started a series of touch-and-go(es) on runway 28L. The accident occurred during the ninth go-around to runway 28L.

(ADS-B data section will be written soon I promise)

According to Air Traffic Control (ATC) communications, the controller informed N734ZK about traffic on 2 mile final for the parallel runway (28R) and cleared them to land on runway 28L. N734ZK acknowledged the message and stated they were looking for traffic. A few seconds later, N734ZK informed the controller they were going around. The controller told N734ZK to extend upwind and that traffic was 11 o'clock about a mile and a half entering the left downwind for the parallel runway. N734ZK responded that he was extending down upwind. The controller then told N734ZK to use caution because he was drifting to the north because traffic (a citation mustang) was departing in trail to westbound. N734ZK responded that they were correcting to the south. The controller then asked N734ZK to turn crosswind at Cessna for the parallel and "pass off your left". N734ZK responded that they were turning left "crosswind traffic in sight." The controller then said "Cessna 4ZK, and give it to you, Cessna mile ahead of you in the stadium, they're gonna turn base for the parallel number 1, runway 28L, cleared for the option, additional traffic approaching a 1 mile final for the parallel on the other side." N734ZK responded: "Yeah, looking for traffic ahead and you said we're number 1? 4ZK" The controller responded: "4ZK, affirmative, number 1, runway 28L cleared for the option." N734ZK then said: "okay, number 1, 28L, cleared for the option, 4ZK." A few seconds later, the controller said "Cessna 4ZK, on traffic for the parallel for your right." N734ZK responded that traffic was in sight. The controller then started talking to a different airplane and reported that winds were 310 at 17 knots gusting 22 knots. When the controller said this, The pilot of N734ZK said that they were going around. 4 seconds later, an impact sound was heard from N734ZK. The controller then told the other airplane on approach that "they just had an accident" and that the airport will be closed, shortly afterwards there was a 5-second transmission from N734ZK that suggests one of the pilots was screaming. There were no more transmissions from the accident airplane.

Witnesses at the airport stated that the airplane entered a stall/spin during the attempted go-around and struck the ground hard. A post crash fire ensued which prevented witnesses from reaching the occupants. Another witness on site stated: "Student and instructor third attempt at landing 28L, 40ยบ, crosswind 13-16 knots, stall/spin into the hold short line for 28L."

- Pilot Information:
Unknown at this point.

- Airplane Information:
The four-seat, high wing, fixed gear airplane, serial number 17269243, was manufactured in 1977. It was powered by a Lycoming O-320 engine.

According to the Pilot Operating Handbook (POH):

BALKED LANDING

In a balked landing (go-around) climb, reduce the wing flap setting to 20" immediately after full power is applied. If obstacles must be cleared during the go-around climb, reduce the wing flap setting to 10° and maintain a safe airspeed until the obstacles are cleared. Above 3000 feet, lean the mixture to obtain maximum RPM. After clearing any obstacles, the flaps may be retracted as the airplane accelerates to the normal flaps-up climb speed.

MANEUVER LIMITS

NORMAL CATEGORY

This airplane is certificated in both the normal and utility category. The normal category is applicable to aircraft intended for non aerobatic operations. These include any maneuvers incidental to normal flying, stalls (except whip stalls), lazy eights, chandelles, and turns in which the angle of bank is not more than 60°. Aerobatic maneuvers, including spins, are not approved.

The stall speed (CAS) with flaps up, power off was 50 knots, the stall speed (CAS) with flaps down, power off was 44 knots.

Stalls

The stall characteristics are conventional and aural warning is provided by a stall warning horn which sounds between 5 and 10 knots above stall in all configurations.

Power-off stall speeds at maximum weight for both forward and aft c.g. positions are presented in Section 5.

STATL SPEEDS

CONDITIONS:

  • Power Off
NOTES:
  • 1. Maximum altitude loss during a stall recovery may be as much as 180 feet.
  • 2. KIAS values are approximate
Figure 5: Stall Speeds

- Wreckage and Impact Information:
The airplane came to rest upright on the shortline holding point for runway 28L. There was a post crash fire that consumed the passenger cabin. Both wings and tail remained attached to the airframe, and there was no debris field leading to the main wreckage. The wings and tail showed little to no impact damage. The impact appears consistent with a flat aerodynamic stall/spin with little to no forward airspeed.

Figure: Last ADS-B data point compared to accident site location

Figure: Airplane at rest

- Airport Information:
The Montgomery-Gibbs Executive Airport is a public airport located six miles north of downtown San Diego, California. The airport covers an area of 456 acres and features three runways, one public helipad, and two private helipads. The runways are 28R/10L and 28L/10R (parallel) and 5/23. The airport field elevation is 427.3 ft.

Runway 10R/28L is 3401 x 60 ft.

- Weather:
(1) Brief:

The KMYF weather observation recorded at 1653 noted: winds from 320 at 17 knots, visibility 10 statute miles, no clouds under 12,000 ft (CLR), temperature 32°C, dew point 18°C, and an altimeter setting of 29.83 inches of mercury (inHg). The calculated density altitude was 2637 ft.

The KMYF weather observation recorded at 1753 noted: winds from 330 at 16 knots, visibility 10 statute miles, no clouds under 12,000 ft (CLR), temperature 32°C, dew point 18°C, and an altimeter setting of 29.84 inches of mercury (inHg).

(2) METARs:

METAR KMYF 072353Z 32017KT 10SM CLR 32/18 A2983 RMK AO2 SLP094 T03170183 10378 20317 55006

METAR KMYF 080053Z 33016KT 10SM CLR 32/18 A2984 RMK AO2 SLP098 T03170178

(3) Area Forecast Discussion:

Mooney M20F Executive 21, N9546M, fatal accident occurred on September 7, 2026, near Space Coast Regional Airport (TIX/KTIX), Titusville, Florida

This is preliminary information, subject to change, and may contain errors. Any errors in this writing will be corrected when/if the NTSB preliminary report is released.

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N9546M

- History of Flight:
On September 7, 2026, at about 1015 local time, a privately-registered Mooney M20F Executive 21, N9546M, was destroyed when it was involved in an accident near Space Coast Regional Airport (TIX/KTIX), Titusville, Florida. The pilot was fatally injured. The flight was originating at the time. 

According to Automatic dependent surveillance-broadcast (ADS-B) data, at 1014:39, the airplane was first seen about 4300 ft down the 7300 ft runway traveling at 71 knots groundspeed with a positive vertical rate of 380 feet per minute (fpm). The next data point was recorded at 1014:48 and showed the airplane at 75 ft, 67 knots groundspeed, with a 0 vertical rate. At 1015:07, the airplane was seen over the departure end of the runway at 125 ft and 60 knots groundspeed with a +640 fpm vertical rate. For the next 7 seconds, the airplane barely climbed to 150 ft while in a left turn, with the groundspeed going up to 67 knots and the vertical rate going down to 128 fpm. In the next 5 seconds, the airplane descended to 125 ft, 65 knots, and -256 fpm. The last ADS-B data point was recorded at 1015:19, the airplane was at 150 ft, 60 knots, and +320 fpm, still in the left turn and over the powerlines that run parallel to the highway.

Figure 1: Entire track with first data point distance calculation

Figure 2: End of track with 1, presumed accident location, and 2, powerlines running along highway

Figure 3: View of end of track with extend to ground option disabled, note powerlines

Figure 4: Raw ADS-B data view

Figure 5: TOC as seen from Flysto

The NTSB reported that the airplane experienced an engine failure on takeoff and crashed into powerlines and terrain. The wreckage was moved before the NTSB investigator in-charge (IIC) arrived on scene.

- Pilot Information:
The registered owner holds a private pilot certificate that was last issued/updated on 2/26/2012 with an airplane single engine land rating. His BasicMed Course was dated 1/18/2025. (It is unknown if this was the accident pilot at this time)

- Airplane Information:
The accident airplane, serial number 670123, was manufactured in 1967. It was a four-seat, low-wing, retractable landing gear airplane powered by a four-cylinder, fuel-injected, horizontally opposed, air-cooled Lycoming IO-360 engine.

- Wreckage and Impact Information:
The airplane impacted powerlines and terrain 0.24 mile north of the departure end of runway 36. The airplane came to rest inverted and was consumed by a post crash fire. Both outer wings were impact damaged and separated, the fuselage and tail showed extensive crush impact damage in various directions. The fuselage was destroyed.

Figure: Tail crushing damage


Figure: Aft view of airframe and tail

- Airport Information:
KTIX is a controlled public airport located 5 miles south of Titusville, Florida. The airport field elevation is 34 ft. The airport features two runways, runway 18/36 asphalt/grooved 7319 x 150 ft, and runway 9/27 asphalt 5000 x 100 ft.

The area north of the airport (and in the path of departure from runway 36) is mostly covered with trees. There is a highway that runs perpendicular to the runway, and the outer side of the highway features powerlines that run parallel to it.

There is a small open field located behind the powerlines and is not covered with trees, given the ADS-B data, the pilot was most likely aiming to land at that area when the accident happened.

Figure: Flight-track with open area to the north of the runway

- Weather:

(1) Brief:

At 1014, KTIX was reporting calm winds, visibility 7 miles, a scattered ceiling at 1,000ft AGL, and an altimeter setting of 29.98 inches of mercury.

At 1015, a nearby airport, Arthur Dunn Air Park (X21), was reporting calm winds, 10 miles visibility, no clouds under 12,000ft (CLR), temperature 28°C, dewpoint 28°C, and an altimeter setting of 29.95 inches of mercury. Distant lightning was reported from the southwest and west. The calculated density altitude was 1552 ft.

(2) METARs:

METAR KTIX 071347Z 02005KT 7SM SCT010 BKN050 A2997=

SPECI KTIX 071414Z 00000KT 7SM SCT010 A2998 <<<<

METAR KTIX 071447Z 00000KT 7SM SCT012 BKN050 A2998=

METAR KX21 071355Z AUTO 00000KT 10SM FEW012 29/28 A2994 RMK AO2 LTG DSNT W

METAR KX21 071415Z AUTO 00000KT 10SM CLR 28/28 A2995 RMK AO2 LTG DSNT SW AND W <<<<

METAR KX21 071435Z AUTO 00000KT 10SM CLR 29/28 A2995 RMK AO2 LTG DSNT SE AND SW

(3) Area Forecast Discussion:

Piper PA-28-181 Archer II, N7653F, fatal accident occurred on September 5, 2026, near Ludlow, Massachusetts

This is preliminary information, subject to change, and may contain errors. Any errors in this writing will be corrected when/if the NTSB preliminary report is released.

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N7653F

- History of Flight:
On September 5, 2026, at about 2103 local time, a Piper PA-28-181 Archer II, N7653F, was destroyed when it was involved in an accident near Ludlow, Massachusetts, The two occupants onboard were fatally injured. The airplane was registered to Hyldburg Aviation Inc, doing business as Alpha One Flight Services, both out of Plymouth, MA. The night-time personal flight originated from Northampton Airport (7B2), Northampton, Massachusetts, and was destined to Plymouth Municipal Airport (PYM/KPYM), 
Plymouth, Massachusetts.

The airplane was based out of KPYM and was frequently conducting local training flights around that airport. On September 5, 2026, at 1104, the pilot rented the airplane and departed KPYM with an intended destination of 7B2. The airplane landed there at 1217. The accident occurred during the return trip.

According to Automatic dependent surveillance-broadcast (ADS-B) data, at 2054, the airplane appears to have departed runway 14 at 7B2 and proceeded on magnetic heading of ~120 degrees and to an inflight cruising altitude of 5,000 ft. At 2102:35, the airplane turned right towards to a magnetic heading of ~180 degrees. At 2102:49, the airplane turned left and reached a top of climb altitude (TOC) of 5,300 ft. The airplane continued to turn left, while maintaining that altitude, and the groundspeed was noted to go down from 103 knots to 77 knots when the airplane initiated a secondary climb to 5,600 ft during the turn. At 2103:35, the airplane stopped the climb and entered a descending right hand turn, which devolved into a spiral. At 2103:56, the last ADS-B data point was recorded in the general vicinity of the accident site. The airplane was seen at 3,800 ft, 171 knots groundspeed, with an average rate of -9000 feet per minute (fpm).

Figure 1: ADS-B exchange track ran through Flysto

Figure 2: Initial TOC

Figure 3: Rapid climb during left turn before the second TOC

Figure 4: Rapid spiral after second and final TOC

Figure 5: End of track

Figure 6: Raw ADS-B exchange overview

- Pilot Information:
None.

- Airplane Information:
The accident aircraft, serial number 28-7790205, was manufactured in 1976. It was a fixed tricycle gear, 4-seat, low-wing airplane powered by a Lycoming O&VO-360 SER engine.

According to the Pilot Operating Handbook (POH):

The airplane is approved for the following operations when equipped in accordance with FAR 91 or FAR 135.

(a) Day V.F.R.

(b) Night V.F.R.

(c) Day I.F.R.

(d) Night I.F.R.

(e) Non Icing

According to the POH, the Never Exceed Speed (Vne) is 171 MPH (148 KTS) CAS.

- Wreckage and Impact:
The airplane impacted wooded terrain and was destroyed by impact forces before coming to rest in a body of water. There was no post crash fire. There was a small debris field leading to the main wreckage. The wreckage appears consistent with a high speed, nose down impact.

- Weather:
(1) Brief:

At 2055, the nearest airport was reporting winds 090 at 3 knots, 10 miles visibility, a broken cloud layer at 3,800ft AGL, an overcast ceiling 10,000ft AGL, temperature 19 °C, dewpoint 16 °C, and an altimeter setting of 29.86 inches of mercury.

(2) METARs:

METAR KCEF 060055Z AUTO 09003KT 10SM BKN038 OVC100 19/16 A2986 RMK AO2 SLP114 T01870163

METAR KCEF 060154Z AUTO 07004KT 10SM FEW008 SCT027 BKN041 OVC050 18/16 A2987 RMK AO2 SLP118

Other nearby airports:

METAR KORH 060054Z 09005KT 8SM -RA FEW008 OVC037 16/15 A2993 RMK AO2 RAE06B48 SLP135 P0000 T01560150 $

METAR KORH 060154Z AUTO 00000KT 6SM RA BR BKN045 OVC060 15/14 A2993 RMK AO2 RAE05B49 SLP134 P0000 T01500139 $

METAR KBAF 060053Z 02003KT 10SM FEW037 BKN060 OVC095 19/16 A2989 RMK AO2 SLP122 T01940161

METAR KBAF 060153Z 11007KT 10SM BKN017 BKN032 OVC060 19/16 A2990 RMK AO2 SLP124 T01940161

(3) Area Forecast Discussion: