# NTSB LAX07LA099: Mallian Rocket II, N789JM, Arvin, CA, March 3, 2007 - Type: NTSB accident investigation - Classification: Accident · Fatal · Limited investigation · Final report - Date: March 3, 2007, 09:45 local (17:45 UTC) - Place: Arvin, CA - Coordinates: 35.223331, -118.841941 - Nearby events: https://openairdocs.org/map.md?lat=35.2233&lon=-118.8419&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Highest injury: Fatal - Injuries: 1 fatal - Status: Completed, report May 28, 2008 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 65372 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX07LA099 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/65372/pdf - Page: https://openairdocs.org/ntsb/LAX07LA099 ## Probable cause Loss of control during cruise for undetermined reasons. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - in flight, cruise - reason for occurrence undetermined, pilot in command (cause) - In flight collision with terrain/water, descent - uncontrolled - terrain condition - ground ## Analysis A flight of six airplanes, including the accident airplane, were returning back to their home airport following a morning flight. The route of flight took the group of airplanes over a local mountain range, which had turbulent weather conditions. Another pilot in the group reported that the winds aloft were between 40 to 70 knots over the mountains, and that he and his passenger were thrown about inside the cockpit. The pilot further reported that during the flight back, there were no radio communications from the accident pilot. Witnesses reported seeing the airplane flying low and fast over a vineyard, and it was then observed in a nose-down attitude that continued to ground impact on flat terrain. The witnesses did not hear any unusual engine sounds prior to the airplane's impact with the ground. The accident site was about 8 miles from the mountain range. Radar data showed that a target identified as the accident airplane was established at 4,900 feet (4,400 agl) at 250 knots. The radar target was then observed to enter a rapid descent to 2,800 feet (2,300 feet agl) prior to dropping off the radar. An inspection of the airframe and engine revealed no obvious mechanical anomalies that would have precluded normal operation. ## Factual narrative HISTORY OF FLIGHT On March 3, 2007, at 0945 Pacific standard time, an experimental Mallian Rocket II, N789JM, impacted flat terrain near Arvin, California. The private pilot/owner operated the single engine airplane under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The pilot, the sole occupant, was killed; the airplane was destroyed. Visual meteorological conditions prevailed for the local area flight, and no flight plan had been filed. The flight departed Mojave Airport (MHV), Mojave, California, at an undetermined time, and was returning to Meadows Field Airport (BFL), Bakersfield, California, at the time of the accident. A Federal Aviation Administration (FAA) inspector interviewed a pilot that had flown with the accident pilot the day of the accident. He reported that a group of six airplanes, including the accident airplane, had flown to MHV for breakfast. Coming back over the Tehachapi Mountains, they experienced turbulence. When they arrived back at the airport, the accident airplane was not with them. They waited for about an hour for the accident pilot to return, and then contacted the tower at Bakersfield, where they were informed that the airplane had crashed. Another pilot reported that the winds were between 40 to 70 knots above the mountains, and that he and his passenger were thrown about inside the cockpit. The pilot further reported that during the flight back, there were no radio communications from the accident pilot. Witnesses in the area reported to responding deputies from the Kern County Sheriff's Department that they observed the airplane flying low and fast over the vineyard. One witness, at her residence, reported seeing the airplane flying low from south to north and then heard "a noise" and saw the airplane crash into the vineyard. Other witnesses reported from their various locations that when they observed the airplane it was in a nose down attitude before it struck the ground. The witnesses did not hear any abnormal sounds emanating from the engine prior to impact. Bakersfield tower identified a visual flight rules (VFR) radar target, 1200 beacon code, at the time of the accident near the accident site. FAA inspectors reviewed the radar data that displayed a VFR radar target at 4,900 feet mean sea level (msl) at a ground speed of 250 knots. The radar showed a rapid descent of the target to 2,800 feet msl. The radar target dropped off radar shortly thereafter. The accident site was located about 8 miles east of the Tehachapi Mountain range. PERSONNEL INFORMATION The pilot's personal logbook was not recovered. Pilot information contained in the report was obtained by reviewing the information on file with the FAA airman and medical information in Oklahoma City, Oklahoma. The 54-year-old private pilot retained a foreign based Canadian license. His FAA issued pilot certificate was issued based on his Canadian license. The private pilot held an airplane single engine land rating, which held the following limitations: Limited to aircraft of 4,000 pounds or less Issued on basis of, and valid only, when accompanied by Canadian License XDP 363032 Not valid for agricultural aircraft operations The pilot was issued a third-class medical dated March 3, 2006. His medical had the limitation that the pilot must wear corrective lenses. AIRCRAFT INFORMATION The airplane was a single engine experimental amateur built Mallian Rocket II, serial number 001. An experimental Textron Lycoming IO-540-EXP, serial number L-51939-06, powered the airplane. The airworthiness certificate was issued on December 14, 2006. The airplane's operating limitations were issued on January 22, 2007, by the FAA Fresno Flight Standards District Office, Fresno, California. Aircraft logbooks were not recovered for the accident airplane. Information obtained for this report was gathered from the airplane's registration on file with the FAA, Oklahoma City. MEDICAL AND PATHOLOGICAL INFORMATION The Kern County Sheriff's Department, Coroner Division, performed an autopsy on the pilot on March 5, 2007. The cause of death was listed as multiple blunt force trauma due to an accident. The FAA Forensic Toxicology Research Team CAMI, Oklahoma City, performed a toxicological analysis from samples obtained during the autopsy. Toxicological testing for carbon monoxide, cyanide, and volatiles yielded negative results. The volatiles section further reported that ethanol was not detected in either the muscle or the kidney. The results for tested drugs yielded the following positive results; diphenhydramine was detected in the spleen and kidney. METEOROLOGICAL INFORMATION A review of the recorded weather data for BFL showed variable to calm wind conditions. Meteorological Terminal Aviation Routine Weather Report (METAR) data for 0854 reported variable winds at 4 knots. At 0954, reported winds were calm, and at 1054, reported winds were variable at 5 knots. WRECKAGE AND IMPACT INFORMATION The airplane came to rest in a vineyard; the engine and propeller assembly was buried about 6 feet in the ground, with the main wreckage lying on top of it. One propeller blade remained attached at the propeller hub. The other blade separated near the butt end of the blade. Both blades showed leading and trailing edge gouging and chordwise scratching, as well as s-bending. TEST AND RESEARCH The airframe inspection revealed no mechanical anomalies, and all four corners of the airplane were present (wings, tail section, cabin, seats, instrument panel, engine, propeller assembly). The airframe rivet holes exhibited a 45-degree angle separation from their respective rivets. A visual examination of the engine revealed that it had been displaced from its engine mounts, with no obvious mechanical damage that would have precluded normal operation. Further examination of the engine revealed no evidence of preimpact mechanical malfunction. ## Aircraft - Registration: [N789JM](https://openairdocs.org/deregistered/N789JM-2014-11-18), registration cancelled 2014-11-18, S/N 001, built 2006 (OpenAirDocs) - Reported make and model: Mallian Rocket II - Registry model: [Mallian Jasbir MALLIAN ROCKET II](https://openairdocs.org/model/mallian-jasbir-mallian-rocket-ii) (registry code 05622KS) (OpenAirDocs) - Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41585, reciprocating) (OpenAirDocs) - Category: Airplane, amateur-built - Serial number: 001 - Engines: Textron Lycoming IO-540-EXP reciprocating - Damage: Destroyed - Flight: Personal, Part 91 - Registered owner: Jasbir S. Mallian - Airworthiness certificate: Special, Experimental (Special) - Departed: MHV, Mojave, CA - Destination: BFL, Bakersfield, CA ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 54; injuries: fatal; private, foreign; airplane ratings: single-engine land; medical: class 3; last flight review July 1, 2006; toxicology performed; flight hours: 1,350 total, 300 in this make and model, 26 in the last 90 days ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 9 statute miles - Lowest ceiling: none - Temperature: 54 °F, dew point 36 °F - Altimeter: 30.29 inHg - Observed at: BFL, 15 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 20070303002379A](https://openairdocs.org/incident/20070303002379A), Mar 3, 2007: Mallia MALLIANRKTII, Arvin, CA, Destroyed, 1 fatal. (-23) This experimental "harmon rocket" crashed in a vineyard near Arvin, CA. The aircraft was destroyed and the pilot suffered fatal injuries. Since there was… 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.