# NTSB WPR26FA330: Cessna 172N, N734ZK, San Diego, CA, September 8, 2026 - Type: NTSB accident investigation - Classification: Accident · Fatal · Class 3 · Field · Preliminary report - Date: September 7, 2026, 17:20 local (Sep 8, 2026, 00:20 UTC) - Place: San Diego, CA - Coordinates: 32.813045, -117.13554 - Nearby events: https://openairdocs.org/map.md?lat=32.8130&lon=-117.1355&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR go-around: Aerodynamic stall/spin](https://openairdocs.org/ntsb-events/241) - Highest injury: Fatal - Injuries: 2 fatal - Status: Investigation ongoing - Investigation class: Class 3 - NTSB office: Western Pacific Region - Parties: FAA, Lycoming, Textron Aviation - NTSB case key (mKey): 203750 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR26FA330 - NTSB preliminary report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/203750/pdf - Page: https://openairdocs.org/ntsb/WPR26FA330 ## Preliminary report On September 7, 2026, about 1720 Pacific daylight time, a Cessna 172N, N734ZK, was destroyed when it was involved in an accident near San Diego, California. The flight instructor and student pilot were fatally injured. The airplane was being operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. Preliminary ADS-B data showed the airplane departed Montgomery-Gibbs Executive Airport (MYF), San Diego, California about 1615. The airplane remained in the local airport traffic pattern for the duration of the accident flight, performing nine left-hand visual traffic patterns to runway 28L. Airport and nearby business security cameras captured portions of the accident flight as the airplane approached the runway and as the pilots performed multiple go around maneuvers. Witnesses also observed the airplane and described the airplane as flying very erratically during multiple go-around maneuvers, pitching upward steeply after the go-around was initiated, flying very slow, and “stalling” before the airplane recovered. On the nineth approach the airplane can be seen in one of the videos flying low near the ground as it approached the runway, nosing over, pitching up and then nosing over a second time. The airplane then entered a steep nose high pitch attitude prior to the runway 28L threshold. The airplane appeared to attain about 45° pitch up attitude while about 100 to 200 ft above ground level. The airplane entered a steep left descending turn and impacted runway 28L near the runway threshold. The airplane came to rest on taxiway B and a post impact fire ensued. The wreckage was examined on scene. The fuselage, inboard wings, and cowling sustained heavy thermal damage. The inboard sections of both wing fuel tanks were partially consumed by fire. All primary flight controls were identified at the accident site. Flight control continuity was confirmed from the cockpit controls to each flight control surface. The engine was examined and the crankshaft was rotated in its normal direction of rotation. Thumb compression was obtained on all four cylinders. Equal movement of all intake and exhaust rocker arms was observed on all cylinders. The aluminum fixed pitch 2-blade propeller remained attached to the crankshaft propeller flange. Blade “A” exhibited rearward bending and torsional twisting along its blade length with its tip missing. Blade “B” was mostly thermally consumed by the post impact fire. Two sections of propeller tip were found between the initial impact marks and the main wreckage. Each portion of blade tip found was twisted, fractured, and heavily scored. No anomalies were identified that would have precluded the normal production of engine power. ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR go-around: Aerodynamic stall/spin](https://openairdocs.org/ntsb-events/241) (defining event); cases with it: [Cessna 172N, 21 cases](https://openairdocs.org/ntsb-events/241/sequence.md?model=2072434), [All aircraft, 1,529 cases](https://openairdocs.org/ntsb-events/241/sequence.md) ## Aircraft - Registration: [N734ZK](https://openairdocs.org/aircraft/N734ZK), registered now, S/N 17269243, built 1977 (OpenAirDocs) - Reported make and model: CESSNA 172N - Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17269243 - Year built: 1977 - Damage: Destroyed - Fire: On-Ground - Flight: Instructional, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, May 28, 2026 - Airport: MYF, Montgomery-Gibbs Exec, runway 10R/28L, 3,401 × 60 ft, asphalt - Equipment: Unknown ## Weather - Conditions: Visual (VMC), Day - Wind: 330° at 16 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 91 °F, dew point 64 °F - Altimeter: 29.83 inHg - Observed at: KMYF - METAR: KMYF 080020Z 33016KT 10SM CLR 33/18 A2983 520 41 2700 320/16 RMK AO2 T03280183 ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20260907012679A](https://openairdocs.org/incident/20260907012679A), Sep 7, 2026: Cessna 172N, San Diego, CA, Destroyed, 2 fatal. On 09/07/2026 at 1719 CFI [privacy data omitted] and student pilot [privacy data omitted] on board aircraft [privacy data omitted] were on a training flight at… ## Other investigations on N734ZK (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB LAX94LA238](https://openairdocs.org/ntsb/LAX94LA238), Jun 4, 1994: Cessna 172N (N734ZK), Valencia, CA, substantial damage. Probable cause: the pilot's selection of an unsuitable field for an off-airport landing and attempted takeoff. From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.