# NTSB WPR09FA192: Piper PA-24-250, N7690P, San Diego, CA, April 11, 2009 - Type: NTSB accident investigation - Classification: Accident · Fatal · Field investigation · Final report - Date: April 11, 2009, 10:54 local (17:54 UTC) - Place: San Diego, CA - Coordinates: 32.88639, -117.047225 - Nearby events: https://openairdocs.org/map.md?lat=32.8864&lon=-117.0472&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Defining event: [Enroute-descent: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: Fatal - Injuries: 2 fatal - Status: Completed, report April 22, 2010 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Piper Aircraft Company, National Air Traffic Controllers Association, Federal Aviation Administration - NTSB case key (mKey): 73637 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR09FA192 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/73637/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=73637 - Page: https://openairdocs.org/ntsb/WPR09FA192 ## Probable cause The pilot's failure to maintain control during an en route cruise descent through multiple cloud layers, resulting in an in-flight breakup. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters](https://openairdocs.org/ntsb-findings/01062000): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-24-250, 6 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md?model=7102404), [All aircraft, 1,269 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md) - [Perception/orientation/illusion: spatial disorientation](https://openairdocs.org/ntsb-findings/02022025): Personnel issues › Psychological · Pilot (probable cause); cases with it: [Piper PA-24-250, 1 case](https://openairdocs.org/ntsb-findings/02022025/cases.md?model=7102404), [All aircraft, 358 cases](https://openairdocs.org/ntsb-findings/02022025/cases.md) - [Ceiling/visibility/precip: clouds](https://openairdocs.org/ntsb-findings/03035025): Environmental issues › Conditions/weather/phenomena · Contributed to outcome; cases with it: [Piper PA-24-250, 3 cases](https://openairdocs.org/ntsb-findings/03035025/cases.md?model=7102404), [All aircraft, 108 cases](https://openairdocs.org/ntsb-findings/03035025/cases.md) - [Wing structure: spar (on wing)](https://openairdocs.org/ntsb-findings/01035711): Aircraft › Aircraft structures · Capability exceeded (probable cause); cases with it: [Piper PA-24-250, 1 case](https://openairdocs.org/ntsb-findings/01035711/cases.md?model=7102404), [All aircraft, 43 cases](https://openairdocs.org/ntsb-findings/01035711/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute-descent: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Piper PA-24-250, 22 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=7102404), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Uncontrolled descent: Aircraft structural failure](https://openairdocs.org/ntsb-events/337); cases with it: [Piper PA-24-250, 3 cases](https://openairdocs.org/ntsb-events/337/sequence.md?model=7102404), [All aircraft, 290 cases](https://openairdocs.org/ntsb-events/337/sequence.md) - [Uncontrolled descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-24-250, 55 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7102404), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis During the pilot's preflight weather briefing for the cross-country flight, he was informed that while a portion of his anticipated hour-long flight could likely be flown under visual flight rules, instrument meteorological conditions, including multiple cloud layers, could be expected approaching his destination. The destination area was covered by a marine cloud layer, with cloud tops of 5,500 feet. En route, the pilot cruised at 7,000 feet. Initially, all air traffic control (ATC) communications with the pilot were routine. An airport located about 6 miles from the accident site reported a broken sky condition at 2,500 and 3,100 feet, and an overcast sky condition at 4,800 feet. As the pilot entered this area, located about 29 miles north of his destination, he informed the terminal radar approach controller that he was descending from 6,200 to 4,000 feet msl. A radar controller acknowledged the pilot's statement. Two and one-quarter minutes later the radar controller instructed the pilot to descend to 2,600 feet, and "keep your speed up." About 5 seconds later, the pilot responded "two thous." The remainder of the pilot's transmission was either interrupted or not recorded, and there were no further communications with the pilot. A review of the recorded radar data and the wreckage distribution evidence indicated that the airplane broke apart after entering instrument meteorological conditions. The structural failure occurred while the airplane was descending at 6,000 feet per minute and in a clockwise turn. The subsequent examination of the airplane revealed that both wings failed in an upward (positive G) direction, consistent with a pilot-induced structural overload. Thereafter, a portion of the right wing impacted the stabilator's right side, which caused it to separate from the airplane. No evidence of any preexisting structural weakness was found during the examination of the heavily fire-damaged main wreckage. ## Factual narrative HISTORY OF FLIGHT On April 11, 2009, about 1054 Pacific daylight time, a Piper PA-24-250, N7690P, experienced an in-flight breakup during an uncontrolled descent in instrument meteorological condition, in San Diego, California. The airplane was destroyed during the breakup sequence and post impact ground fire. The private pilot owned and operated the airplane, and he and his passenger were killed. The personal flight was performed under an instrument flight rules (IFR) flight plan and under the provisions of 14 Code of Federal Regulations Part 91. The flight to the Brown Field Municipal Airport (SDM) in San Diego originated from the Whiteman Airport, Los Angeles, California, about 1004. The flight commenced in visual meteorological conditions (VMC). According to the Federal Aviation Administration (FAA), the pilot did not report experiencing any difficulties or abnormal conditions during the flight. While en route, the pilot cruised at 7,000 feet mean sea level (msl). The pilot transitioned from VMC to instrument meteorological conditions (IMC) approaching San Diego. IMC existed in the accident site area. At 1050:34, when the southbound pilot was approximately 29 miles north of SDM, he informed FAA Southern California Terminal Radar Approach Control (SOCAL) that he was descending from 6,200 to 4,000 feet msl. The radar controller acknowledged the pilot's statement at 1050:45. Two and one-quarter minutes later, about 1053:04, the radar controller instructed the pilot to "descend and maintain two thousand six hundred keep your speed up." Five seconds later, at 1053:09, the pilot responded "two thous." The remainder of the pilot's transmission was either interrupted or not recorded by SOCAL. There were no further communications with the pilot. The FAA subsequently reported to the National Transportation Safety Board investigator that all previous communications with the accident pilot had been routine. According to the airplane's Mode C altitude reporting transponder, FAA recorded radar indicates that about 2 seconds before the pilot's last transmission, at 1053:07, the airplane's altitude was 4,200 feet. At 1053:11, the airplane was at 3,800 feet, and at 1053:16, the airplane was at 3,300 feet. The airplane's average descent rate during this 9-second interval was about 6,000 feet per minute, and the southbound airplane's course was changing in a clockwise direction. By 1053:16, the airplane was on a westerly course, and there were no further recorded radar hits. Two ground-based witnesses reported hearing the accident. The first witness stated that he heard the sound of an airplane diving. The airplane's engine was at a high rpm, and its sound became louder without any variation in power. The sound lasted 5 or 6 seconds. At the time, there was about a 3,000-foot broken ceiling, with unrestricted visibility below the clouds. There was no precipitation. The second witness, who was located about 1/2-mile from the impact site, reported he heard a highpitched sound, like that of an incoming missile. The sound was very loud. Its intensity increased until it terminated with a boom. Seconds thereafter, the witness observed a fireball on a nearby hill. Pieces of irregular shaped wreckage were noted "floating" down near the site of the fireball. At the time the weather was overcast, and it had been misting. PERSONNEL INFORMATION The pilot, age 51, held a private pilot certificate with airplane single engine and instrument ratings. The pilot's last aviation medical certificate was issued in the third class, in July 2008. The certificate bore the restriction that the pilot have available glasses for near vision. On July 29, 2008, the pilot completed an aviation insurance application for the accident airplane. On the application, the pilot indicated that his total flight time was 820 hours. The pilot reported that he had flown 20 hours during the preceding 90 days. Also, his total flight time in the accident model of airplane was 370 hours. A certified flight instructor (CFI) reported to the Safety Board investigator that on August 2, 2008, he had flown in the pilot's airplane for the purpose of giving him a flight review. The pilot successfully completed the review. On December 27, 2008, the CFI also flew with the pilot. On this date, the pilot practiced instrument flying, which included performing three instrument approaches (two VOR and one ILS). AIRCRAFT INFORMATION The airplane was maintained on an annual inspection basis. Acquaintances of the pilot reported to the Safety Board investigator that the pilot had, on occasion, performed maintenance on his airplane. An FAA certificated mechanic reported that he believed some of the maintenance the pilot performed had not been supervised by a licensed mechanic, as required by federal regulations. The 48-year-old accident airplane had been modified from its original Piper Aircraft Corporation type design certificate. Upgraded avionics and accessories had been installed since the airplane's date of manufacture in 1961. Some of the modifications included installation of a 3-blade propeller, engine exhausts, one piece windshield, Lopresti speed enhancement devices, wingtips, and avionics including a multifunction instrument display, engine performance analyzer, and an autopilot. Family members reported that the airplane had received an "owner-assisted" annual inspection a few weeks prior to the accident. METEOROLOGICAL INFORMATION At 0827, the pilot telephoned the Prescott Automated Flight Service Station (AFSS) and received a weather briefing for his flight to San Diego. The pilot told the AFSS briefer that he was planning to fly under VFR to the Brown Field. The cruise altitude was 5,500 feet msl, and the flight's duration was 1 hour. The briefer inquired if the pilot could fly under IMC. The pilot responded "yes I could." Thereafter, the briefer told the pilot that he did not believe the pilot would need to fly under IFR. However, there was a "marinelayer" present. In pertinent part, the briefer told the pilot that at Whiteman, there were few clouds at 3,000 feet above ground level (agl). An advisory existed for mountain obscuration. Over the Los Angeles basin area there were scattered clouds based around 2,000 to 5,000 feet mean sea level (msl). Inland, the ceiling was overcast, but occasionally a broken condition existed. Scattered cirrus clouds existed aloft. To the south, scattered, broken, and overcast clouds existed with bases from 2,000 to 5,000 feet msl. At the Brown Field, the weather was 2,700 feet scattered, ceiling 4,100 feet overcast, with 10 miles visibility. The briefer stated to the pilot "...looks like you still might need to go IFR, looks like you might be right in the clouds at your altitude." Also, 10 miles northeast of the San Diego Lindbergh airport, broken clouds existed with bases at 4,000 feet, and with cloud tops at 5,500 feet msl. In the San Diego area, no forecast or pilot reports existed for convective weather conditions or icing. The closest aviation weather observation station to the accident site was located at the Miramar Marine Corps Air Station, about 5.7 miles west-southwest (244 degrees) from the accident site. At 1055, Miramar (elevation 478 feet msl) reported a broken sky condition at 2,500 and 3,100 feet, and an overcast sky condition at 4,800 feet agl. The wind was from 210 degrees at 5 knots, and the visibility was 10 miles. The temperature and dew point were 13 and 9 degrees Celsius, respectively. At 1108, Miramar reported a special weather observation. In part, the ceiling was 200 feet broken, 3,000 feet overcast, and 5,000 feet overcast (agl). The visibility was 7 miles. WRECKAGE AND IMPACT INFORMATION Airplane wreckage was located on a hillside about 5.5 miles east-northeast of the Miramar Marine Corps Air Station. The accident site was about 900 feet north-northwest (329 degrees, magnetic) from the airplane's last recorded position on radar. The site was located on an estimated 30-degree downsloping hillside at elevations between 1,000 and 850 feet msl. The magnetic bearing and distance between the initial point of impact (IPI) crater and the main wreckage (cockpit) was about 167 degrees and 50 feet. The majority of the fragmented wreckage was found scattered over a 150-foot-wide by 530-foot-long southeasterly path. All of the flight control surfaces were found in the wreckage area. The separated outer wing sections were not damaged by fire, and they were found near the highest elevations on the hillside, between 100 and 300 feet north of the IPI crater. The engine and main wreckage were located to the south, near the lowest elevations. The inboard wing spans, the vertical stabilizer with attached rudder, and the left stabilator were found attached to the fuselage and were fire-damaged. The instrument panel was fragmented and destroyed by fire, along with the cockpit and cabin which were consumed. None of the components located hundreds of feetaway from the main wreckage were burned. The Safety Board investigator's wreckage examination revealed that the airplane's wing spars were bent and fractured in an upward direction. The right stabilator was found separated from the empennage, and its airframe attachment structure was observed bent in an aft direction. The leading edge of the stabilator was also crushed in an aft direction, and it bore witness marks that were consistent with the deformation pattern from a separated right wing skin component. The engine was found separated from its firewall attachment, and its case was broken open. A visual examination of its exterior surfaces, cylinders, and internal components did not disclose evidence of any preimpact anomalies. Two of the three propeller blades were found in the IPI crater, and the third blade was found several yards away. Two of the blades exhibited tip curl, gouges, and scratches in a chordwise direction. MEDICAL AND PATHOLOGICAL INFORMATION On April 13, 2009, an autopsy was performed on the pilot by the County of San Diego, Office of the Medical Examiner. The autopsy findings indicated the pilot died from "multiple blunt force injuries." Forensic toxicology was performed on specimens from the pilot. The FAA's Civil Aerospace Medical Institute's (CAMI's) Bioaeronautical Sciences Research Laboratory, Oklahoma City, Oklahoma, reported that no ethanol, carbon monoxide, cyanide, or any screened drugs were detected. ADDITIONAL INFORMATION Family members and acquaintances of the pilot reported to the Safety Board investigator that the pilot's wife was ill. The purpose of the flight was for the pilot to fly his wife to southern California where she could receive treatment at a nearby facility. The pilot was familiar with the route of flight, having flown it on several occasions. ## Aircraft - Registration: [N7690P](https://openairdocs.org/deregistered/N7690P-2013-05-09), registration cancelled 2013-05-09, S/N 24-2900, built 1961 (OpenAirDocs) - Reported make and model: PIPER PA-24-250 - Registry model: [Piper PA-24-250](https://openairdocs.org/model/piper-pa-24-250) (registry code 7102404) (OpenAirDocs) - Registry engine: [Lycoming 0-540 series](https://openairdocs.org/engine/lycoming-0-540-series) (registry code 41532, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 24-2900 - Engines: LYCOMING O-540 SERIES 250 horsepower reciprocating - Damage: Destroyed - Fire: On-Ground - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, March 1, 2009 - Departed: WHP, Los Angeles, CA - Destination: SDM, San Diego, CA - Flight plan: IFR ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 51; injuries: fatal; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review August 2, 2009; toxicology performed; flight hours: 820 total, 370 in this make and model, 20 in the last 90 days ## Weather - Conditions: Instrument (IMC), Day - Wind: 210° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: 2,500 ft broken - Temperature: 55 °F, dew point 48 °F - Altimeter: 30.00 inHg - Observed at: NKX, 5 nm away ## 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 20090411004649A](https://openairdocs.org/incident/20090411004649A), Apr 11, 2009: Piper PA24250, San Diego, CA, Destroyed, 2 fatal. (-23) On April 11, 2009, about 1054 pacific daylight time, a Piper PA-24-250, N7690P, owned and operated by the pilot, experienced an in-flight breakup during… ## Other investigations on N7690P (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 IAD71FIJ11](https://openairdocs.org/ntsb/IAD71FIJ11), Nov 8, 1970: Piper PA-24 (N7690P), Independence, VA, substantial damage ## Docket (43 files) The files NTSB released with the investigation on January 26, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=73637. 35.4 MB in all. - Witness Statement - Hufford (item 1, .PDF, 11 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324187&FileExtension=.PDF&FileName=Witness%20Statement%20-%20Hufford-Master.PDF - Witness Statement - Tosheff (item 2, .PDF, 334 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324188&FileExtension=.PDF&FileName=Witness%20Statement%20-%20Tosheff-Redacted.PDF - Record of Conversation - Roberts (item 3, .PDF, 49 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324189&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Roberts-Master.PDF - Wreckage Distribution & Diagram (item 4, .PDF, 90 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324190&FileExtension=.PDF&FileName=Wreckage%20Distribution%20%26%20Diagram-Master.PDF - Weather Reports & PRC Briefing Data (item 5, .PDF, 3.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324191&FileExtension=.PDF&FileName=Weather%20Reports%20%26%20PRC%20Briefing%20Data-Redacted.PDF - Transcripts of Telephone Communications (item 6, .PDF, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324192&FileExtension=.PDF&FileName=Transcripts%20of%20Telephone%20Communications-Redacted.PDF - Transcripts of Radio Communications (item 7, .PDF, 420 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324277&FileExtension=.PDF&FileName=Transcripts%20of%20Radio%20Communications-Redacted.PDF - FAA Form 8020-6, Report of Accident (item 8, .PDF, 33 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324584&FileExtension=.PDF&FileName=FAA%20Form%208020-6,%20Report%20of%20Accident-Master.PDF - Daily Record of Facility Operation (item 9, .PDF, 142 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324193&FileExtension=.PDF&FileName=Daily%20Record%20of%20Facility%20Operation-Redacted.PDF - Report from Piper Aircraft (item 10, .PDF, 14 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324194&FileExtension=.PDF&FileName=Report%20from%20Piper%20Aircraft-Master.PDF - Radar Data & Track Plots (item 11, .PDF, 656 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324195&FileExtension=.PDF&FileName=Radar%20Data%20%26%20Track%20Plots-Master.PDF - Toxicological Report (item 12, .PDF, 106 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324196&FileExtension=.PDF&FileName=Toxicological%20Report-Master.PDF - Statement of Party Representatives to NTSB Investigation (item 13, .PDF, 209 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324197&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Redacted.PDF - Release of Aircraft Wreckage, NTSB Form 6120.15 (item 14, .PDF, 25 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324198&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-Redacted.PDF - Pilot's Insurance Application (item 15, .PDF, 279 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324199&FileExtension=.PDF&FileName=Pilot%27s%20Insurance%20Application-Redacted.PDF - Correspondence (item 16, .PDF, 23 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324200&FileExtension=.PDF&FileName=Correspondence-Redacted.PDF - Photo 1. Flight track, from FlightAware.com (item 17, .PDF, 34 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324202&FileExtension=.PDF&FileName=Photo%201.%20Flight%20track,%20from%20FlightAware.com-Master.PDF - Photo 2. Accident site, overall view. (item 18, .PDF, 1.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324203&FileExtension=.PDF&FileName=Photo%202.%20%20Accident%20site,%20overall%20view.-Master.PDF - Photo 3. Accident site, initial point of impact above main wreckage. (item 19, .PDF, 845 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324204&FileExtension=.PDF&FileName=Photo%203.%20%20Accident%20site,%20initial%20point%20of%20impact%20above%20main%20wreckage.-Master.PDF - Photo 4. Initial point of impact (foreground) & main wreckage (background). (item 20, .PDF, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324205&FileExtension=.PDF&FileName=Photo%204.%20%20Initial%20point%20of%20impact%20(foreground)%20%26%20main%20wreckage%20(background).-Master.PDF - Photo 5. Wreckage distribution path, uphill view. (item 21, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324206&FileExtension=.PDF&FileName=Photo%205.%20Wreckage%20distribution%20path,%20uphill%20view.-Master.PDF - Photo 6. Main wreckage, cockpit area. (item 22, .PDF, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324207&FileExtension=.PDF&FileName=Photo%206.%20%20Main%20wreckage,%20cockpit%20area.-Master.PDF - Photo 7. Vertical stabilizer, rudder & left stabilator. (item 23, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324208&FileExtension=.PDF&FileName=Photo%207.%20%20Vertical%20stabilizer,%20rudder%20%26%20left%20stabilator.-Master.PDF - Photo 8. Instruments. (item 24, .PDF, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324209&FileExtension=.PDF&FileName=Photo%208.%20%20Instruments.-Master.PDF - Photo 9. Engine, bottom overall view. (item 25, .PDF, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324210&FileExtension=.PDF&FileName=Photo%209.%20%20Engine,%20bottom%20overall%20view.-Master.PDF - Photo 10. Engine, accessory gears, aft view. (item 26, .PDF, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324211&FileExtension=.PDF&FileName=Photo%2010.%20Engine,%20accessory%20gears,%20aft%20view.-Master.PDF - Photo 11. Engine, front view & prop flange. (item 27, .PDF, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324212&FileExtension=.PDF&FileName=Photo%2011.%20Engine,%20front%20view%20%26%20%20prop%20flange.-Master.PDF - Photo 12. Prop blades. (item 28, .PDF, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324213&FileExtension=.PDF&FileName=Photo%2012.%20Prop%20blades.-Master.PDF - Photo 13. Prop blade #1. (item 29, .PDF, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324214&FileExtension=.PDF&FileName=Photo%2013.%20Prop%20blade%20%231.-Master.PDF - Photo 14. Prop blade #2 in IPI crater. (item 30, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324215&FileExtension=.PDF&FileName=Photo%2014.%20Prop%20blade%20%232%20in%20IPI%20crater.-Master.PDF - Photo 15. Prop blade #3, cambered side. (item 31, .PDF, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324216&FileExtension=.PDF&FileName=Photo%2015.%20Prop%20blade%20%233,%20cambered%20side.-Master.PDF - Photo 16. Wing spar, right overall. (item 32, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324217&FileExtension=.PDF&FileName=Photo%2016.%20Wing%20spar,%20right%20overall.-Master.PDF - Photo 17. Wing spar, right, close up. (item 33, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324218&FileExtension=.PDF&FileName=Photo%2017.%20Wing%20spar,%20right,%20close%20up.-Master.PDF - Photo 18. Wing spar, left. (item 34, .PDF, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324219&FileExtension=.PDF&FileName=Photo%2018.%20%20Wing%20spar,%20left.-Master.PDF - Photo 19. Wing, left & aileron view. (item 35, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324220&FileExtension=.PDF&FileName=Photo%2019.%20%20Wing,%20left%20%26%20aileron%20view.-Master.PDF - Photo 20. Wing, left & aileron. (item 36, .PDF, 811 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324221&FileExtension=.PDF&FileName=Photo%2020.%20%20Wing,%20left%20%26%20aileron.-Master.PDF - Photo 21. Wing, right with aileron. (item 37, .PDF, 970 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324222&FileExtension=.PDF&FileName=Photo%2021.%20Wing,%20right%20with%20aileron.-Master.PDF - Photo 22. Stabilator, right. (item 38, .PDF, 997 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324223&FileExtension=.PDF&FileName=Photo%2022.%20%20Stabilator,%20right.-Master.PDF - Photo 23. Stabilator (top front view) with right wing skin panel held in position. (item 39, .PDF, 824 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324224&FileExtension=.PDF&FileName=Photo%2023.%20Stabilator%20(top%20front%20view)%20with%20right%20wing%20skin%20panel%20held%20in%20position.-Master.PDF - Photo 24. Stabilator with bottom of wing skin panel held in position. (item 40, .PDF, 975 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324225&FileExtension=.PDF&FileName=Photo%2024.%20Stabilator%20with%20bottom%20of%20wing%20skin%20panel%20held%20in%20position.-Master.PDF - Photo 25. Stabilator, right, aft crushed leading edge. (item 41, .PDF, 799 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324226&FileExtension=.PDF&FileName=Photo%2025.%20Stabilator,%20right,%20aft%20crushed%20leading%20edge.-Master.PDF - Photo 26. Stabilator, right, with 1 of 5 parallel impact marks identified. (item 42, .PDF, 710 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324227&FileExtension=.PDF&FileName=Photo%2026.%20Stabilator,%20right,%20with%201%20of%205%20parallel%20impact%20marks%20identified.-Master.PDF - Photo 27. Stabilator, right, with right wing skin stringer signatures. (item 43, .PDF, 682 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324228&FileExtension=.PDF&FileName=Photo%2027.%20Stabilator,%20right,%20with%20right%20wing%20skin%20stringer%20signatures.-Master.PDF 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.