# NTSB WPR23FA047: Greg Hobbs Lightning, N60MY, Torrance, CA, November 30, 2022 - Type: NTSB accident investigation - Classification: Accident · Fatal · Class 3 · Field · Final report - Date: November 30, 2022, 11:00 local (19:00 UTC) - Place: Torrance, CA · Zamperini Field Airport - Coordinates: 33.8075, -118.34722 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=33.8075&lon=-118.3472&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR pattern final: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: Fatal - Injuries: 2 fatal - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Western Pacific Region - Parties: FAA - NTSB case key (mKey): 106386 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR23FA047 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/106386/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=106386 - Page: https://openairdocs.org/ntsb/WPR23FA047 ## Probable cause The failure of the pilot to maintain control of the airplane while performing a slip maneuver on final approach. Contributing was the failure of the pilot to fly a stabilized approach. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: use of equip/system](https://openairdocs.org/ntsb-findings/02063015): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Greg Hobbs LIGHTNING, 1 case](https://openairdocs.org/ntsb-findings/02063015/cases.md?model=05630W3), [All aircraft, 1,391 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Greg Hobbs LIGHTNING, 1 case](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=05630W3), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Greg Hobbs LIGHTNING, 1 case](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=05630W3), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR pattern final: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Greg Hobbs LIGHTNING, 1 case](https://openairdocs.org/ntsb-events/240/sequence.md?model=05630W3), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) ## Analysis Two pilots were conducting pattern work at the accident airport. Video footage as well as witness statements showed the accident airplane was on final approach to land at a low altitude and high rate of speed. The airplane yawed to the left while in a forward slip, rolled inverted, and descended rapidly in a nose-down attitude. The airplane impacted terrain in a field just short of the runway threshold. Postaccident examination of the airplane’s wreckage revealed no evidence of any preimpact failures or malfunctions that would have precluded normal operation. Overall, the medical investigation for this accident identified that both the pilot and pilot-rated passenger had potentially impairing medical conditions and had used potentially impairing substances. Although an improperly performed slip maneuver could explain the sudden loss of control, and such an improper maneuver might plausibly represent diminished performance related to subtle impairment, the investigation was unable to determine whether a medical factor contributed to the accident based on the available evidence. It is likely that the pilot’s control inputs were too aggressive when the airplane was placed into the forward slip to land, which resulted in the loss of control. Additionally, the pilot failed to fly a stabilized approach by landing too fast. ## Factual narrative According to the Federal Aviation Administration’s Airplane Flying Handbook: “Pilots may consider the following elements when attempting to set up and fly a stabilized approach for landing. AIRSPEED. The aircraft speed is with +10/-5 knots of the recommended landing speed…” According to information provided for the airplane pilot’s operating handbook, at the maximum takeoff weight the flaps up stall speed was 45 knots and the flaps down full stall speed was 40 knots. In addition, the speed for “normal approach, flaps 25°” is 52 knots indicated air speed (KIAS). Zamperini Field Airport was located about 3 miles southwest of Torrance, California. The airport had an operating control tower. Airport remarks mention that the runway’s 11R traffic pattern was to the right and had a 2-box Visual Approach Slope Indicator (VASI) on the left (4° glide path). No obstructions were noted on runway 11R. On November 30, 2022, about 1100 Pacific standard time, an amateur-built experimental Lightning, N60MY, was substantially damaged when it was involved in an accident near Torrance, California. The pilot and pilot-rated passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight. A review of ADS-B data showed that the airplane departed Zamperini Field Airport (TOA), Torrance, California, about 1042. The data showed the airplane flew several traffic patterns at TOA. About 1100, on the 4th traffic pattern and while on final approach, the last data point indicated that the airplane’s altitude was about 200 ft mean sea level, the heading was about 129°, and the ground speed was about 69 knots. Review of the Air Traffic Control tower audio revealed that the pilot established communication with the ground controller with the current automatic terminal information service information and requested to practice pattern work. The controller cleared the pilot for takeoff on runway 11R and then misspoke and cleared the pilot for the option for runway 29R. However, the pilot read back the correct runway, which was runway 11R. On the 4th traffic pattern, as the pilot was turning downwind, the controller cleared him for a touch and go to runway 11R. The pilot did not read back the clearance. A non-intelligible transmission was then broadcast on the frequency. The controller then lost sight of the airplane and attempted to communicate with them. The controller requested an uninvolved airplane to assist with sighting of the accident airplane; however, the controller then observed the position of the accident airplane. The uninvolved airplane was cleared to land on runway 11L. About one minute, after the controller observed the position of the accident airplane, an uninvolved helicopter established communication with the ground controller and advised them that they witnessed the accident airplane go straight down. Witnesses observed the airplane on short final, about 150 ft above ground level, and said that itappeared fast. Shortly thereafter, the airplane yawed left in a forward slip. The airplane then rolled inverted, and descended rapidly in a nose-down attitude and impacted terrain. A review of surveillance videos from near the airport revealed that the airplane was at a low altitude and quickly rolled inverted and before it descended to the ground in a steep nose-low attitude. The Department of Coroner Los Angeles, California, conducted an autopsy on the pilot and the pilot-rated passenger. According to the medical examiner, the cause of the deaths was determined to be from “blunt trauma.” The Federal Aviation Administration's (FAA) Forensic Sciences Research Laboratory, Oklahoma City, Oklahoma, performed toxicological testing on the pilot. The pilot’s results for the testing were positive for Glucose, Doxylamine, Pregabalin, Atorvastatin and Tamsulosin. The pilot had Glucose detected in urine, but the amount detected was not significant. Doxylamine was detected and is an antihistamine used to treat allergies. Doxylamine is like Benadryl and can cause sleepiness. It is also sold as a sleep aid under the name Unisom. Doxylamine is acceptable for pilots if used occasionally for a time-limited condition. There is a 60-hour waiting period before flying. Pregabalin (Lyrica) is a prescription medication used to treat anxiety, epilepsy, diabetic nerve pain, shingles, and fibromyalgia. Pregabalin typically carries a warning that in may cause dizziness and sleepiness and impair users’ ability to drive or operate machinery, and that users should not operate a motor vehicle or do other dangerous activities until they know how the drug affects them. Pregabalin is unacceptable for pilots due to side effects including drowsiness, vertigo, and abnormal thinking. According to the FAA Forensic Sciences laboratory website, the FAA considers pregabalin to be a “Do Not Issue/Do Not Fly” medication. Atorvastatin was detected. Atorvastatin is used to treat high cholesterol and is acceptable for pilots. Tamsulosin was detected. Tamsulosin is an alpha blocker used to treat prostate hypertrophy and is acceptable for pilots. The 81-year-old male pilot’s last aviation medical examination was October 22, 2008. He reported a history of coronary artery disease and coronary artery bypass graft in 1980 and 1991, coronary artery stenting in 2001, diabetes, and high cholesterol. The FAA had granted him Authorization for Special Issuance of medical certification, first in 1999 and most recently in 2006 (the most recent authorization had been for 6 years). At his last aviation medical examination, he was issued a third-class medical certificate with interim issuance, limited by a requirement to have available glasses for near vision, and not valid after October 31, 2009. The pilot subsequently completed a BasicMed education course, most recently in February 2021, and reported completing a BasicMed Comprehensive Medical Examination Checklist (CMEC), most recently in January 2021.Toxicological testing was performed on the pilot-rated passenger. The results for the second pilot were positive for methamphetamine, amphetamine, losartan, loratadine, desloratadine, and metoprolol. Methamphetamine and its metabolite amphetamine were detected. Methamphetamine is a potent Drug Enforcement Agency Schedule II stimulant drug with significant abuse potential. Methamphetamine is commonly used as a recreational drug. However, it also is used in the medical field for the treatment of narcolepsy and obesity. Doses of 10-30 mg methamphetamine have shown to improve reaction time, relief fatigue, improve cognitive function testing, increase subjective feelings of alertness, increase time estimation, and increase euphoria. However, subjects were willing to make more high-risk choices. Expected effects following higher doses may include agitation, inability to focus attention on divided attention tasks, inattention, restlessness, motor excitation, increased reaction time, and time distortion, depressed reflexes, poor balance and coordination, and inability to follow directions. At very high doses, it can induce psychosis and breakdown of skeletal muscle. This medication is disqualifying for FAA aeromedical certification; therefore, use could represent a violation of 14 CFR Part 61.53(a) and/or Part 91.7(a)(3). Losartan was detected. Losartan (Cozaar) is an ACE-II inhibitor-type antihypertensive used to treat high blood pressure and is acceptable for pilots. Loratadine and the metabolite desloratadine were detected. Loratadine (Claritin) is a non-prescription non-sedating antihistamine used to treat allergies. Loratadine is acceptable for pilots. Metoprolol was detected. Metoprolol (Lopressor) is a beta-blocker used to treat high blood pressure and is acceptable for FAA medical certification. A model sounding for the area of the accident site did not identify any significant low-level wind shear. There were no disseminated pilot reports within 1 hour of the accident time within 50 miles of TOA. Additionally, weather radar imagery depicted areas of light precipitation to the south and west but not over the accident location about the time of the accident. According to a friend of the pilot, the first pilot and owner of the airplane had owned it for about 1 1/2 years. The second pilot was a partner in the airplane. The friend talked to both pilots the day before the accident and commented that they both seemed in good spirits. Examination of the accident site revealed that the airplane impacted terrain about 1250 ft short of the approach threshold of runway 11R. The grass field was generally flat with a drainage ditch that was about 1 ft in depth, parallel to the runway, where the airplane impacted. All major components of the airplane necessary for flight were found in the main wreckage with some small fragments of debris scatter about 25 ft from the main wreckage. The front portion of the airplane came to rest pointing downwards toward theground. There was no postimpact fire. Postaccident examination of the airplane’s airframe and engine revealed no evidence of failures or malfunctions that would have precluded normal operation. Flight control continuity was established, and no preimpact anomalies were noted on the engine. ## Aircraft - Registration: [N60MY](https://openairdocs.org/deregistered/N60MY-2023-07-20), registration cancelled 2023-07-20, S/N 125, built 2011 (OpenAirDocs) - Reported make and model: GREG HOBBS LIGHTNING - Registry model: [Greg Hobbs LIGHTNING](https://openairdocs.org/model/greg-hobbs-lightning) (registry code 05630W3) (OpenAirDocs) - Registry engine: [Jabiru 3300](https://openairdocs.org/engine/jabiru-3300) (registry code 34801, 4 cycle) (OpenAirDocs) - Category: Airplane, amateur-built - Serial number: 125 - Year built: 2011 - Engines: JABIRU 3300 120 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Special, Experimental (Special) - Airport: TOA, Zamperini Fld, runway 11R, 3,000 × 75 ft, asphalt - Equipment: Electronic primary flight display ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 81; injuries: fatal; airline transport; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: basicmed, unknown; toxicology performed; flight hours: 19,335 total - Pilot-rated passenger; age 59; injuries: fatal; private; airplane ratings: single-engine land; medical: class 2, without waivers/limitations; toxicology performed; flight hours: 200 total ## Weather - Conditions: Visual (VMC), Day - Wind: 100° at 9 knots - Visibility: 10 statute miles - Lowest ceiling: 2,000 ft broken - Temperature: 63 °F, dew point 54 °F - Altimeter: 30.05 inHg - Observed at: KTOA - METAR: METAR KTOA 301909Z 10009KT 10SM BKN020 BKN030 17/12 A3005 RMK AIRPORT CLOSED DUE TO AN AIRCRAFT MISHAP ## 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 20221130023019A](https://openairdocs.org/incident/20221130023019A), Nov 30, 2022: Arion Aircraft, LLC (Kit) LIGHTNING, Torrance, CA, Destroyed, 2 fatal. On Wednesday, November 30, 2022, at 1905 zulu, 1105 PST, a fatal general aviation accident occured at Torrance, CA (toa). The fatal accident involved 1 pilot… ## Docket (13 files) The files NTSB released with the investigation on December 5, 2024, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=106386. 221 MB in all. - Memorandum for record a�� witnesses and record of email (item 1, PDF, 7 pages, 127 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17961844&FileExtension=pdf&FileName=Memorandum%20for%20Record%20(Witnesses%20and%20Record%20of%20Emails-Rel.pdf - ADS-B data (item 2, CSV, 2.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17907809&FileExtension=csv&FileName=20221130_A7C610_501986336_ADSB-Rel.csv - Ops vue data (item 3, CSV, 32 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17908064&FileExtension=csv&FileName=OPs%20Vue%20Data%201-Rel.csv - Info provide for POH excerpts (item 4, PDF, 2 pages, 161 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17907799&FileExtension=pdf&FileName=Information%20Provided%20for%20POH-Rel.pdf - Airplane flying handbook excerpts (item 5, PDF, 2 pages, 467 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17962146&FileExtension=pdf&FileName=AFH%20Excerpts-Rel.pdf - Accident site summary report (item 6, PDF, 6 pages, 601 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17961501&FileExtension=pdf&FileName=WPR23FA047%20Accident%20Site%20Factual%20Report%20%20Final1-1-Rel.pdf - Toxicological report (item 7, PDF, 1 page, 173 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17907609&FileExtension=pdf&FileName=Tox%20Test%20Pilot_Redacted-Rel.pdf - Toxicological report pilot rated passenger (item 8, PDF, 1 page, 198 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17908165&FileExtension=pdf&FileName=Tox%20Test%20Plot%20Rated%20Pax_Redacted-Rel.pdf - Medical factual memorandum for record (item 9, PDF, 5 pages, 150 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17961008&FileExtension=pdf&FileName=WPR23FA047_MedicalFactualMemo_Final1-Rel.pdf - Airframe and engine examination summary report (item 10, PDF, 6 pages, 382 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17960668&FileExtension=pdf&FileName=Airframe%20and%20Engine%20Examination%20Report-Rel.pdf - Video file courtesy of home depot (item 11, AVI, 8.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17961149&FileExtension=avi&FileName=Parking%20Lot%20Cam_Courtesty_HomeDepot-Rel.avi - Video file courtesy of torrance memorial medical center (item 12, AVI, 207 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17961511&FileExtension=avi&FileName=11%2030%202022%20Torrance%20Airport%20Crash_TorranceMemMedCtr-Rel.avi - Release of aircraft wreckage, NTSB form 6120.15 (item 13, PDF, 1 page, 472 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17950053&FileExtension=pdf&FileName=Signed%20Wreckage%20Release_Redacted-Rel.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.