# N9830: not currently registered

- Registered now: No (not in the FAA registry file). The mark may be reserved or free to assign
- Earlier aircraft: 1
- Last cancelled: February 11, 2000
- FAA registry: https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=9830
- Page: https://openairdocs.org/aircraft/N9830

## Aircraft that carried N9830

- [Cancelled 2000-02-11](https://openairdocs.org/deregistered/N9830-2000-02-11): Grumman Acft ENG Cor-Schweizer G-164A, S/N 1257. Triennial form not returned. Owner: [Chuck Jones Flying Service Inc](https://openairdocs.org/faa-owner/CHUCK%20JONES%20FLYING%20SERVICE%20INC), [Biggs, CA](https://openairdocs.org/faa-place/CA/Biggs)

## NTSB investigations on N9830 (4)

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 LAX95LA192](https://openairdocs.org/ntsb/LAX95LA192), May 19, 1995: Grumman G-164A (N9830), Colusa, CA, substantial damage. Probable cause: the pilot's misjudged flare height and timing, which resulted in an inadvertent stall and hard landing. Factors in the accident were the loss of engine power for undetermined reasons and the lack of…
- [NTSB SEA89LA115](https://openairdocs.org/ntsb/SEA89LA115), Jun 21, 1989: Grumman-Schweizer G-164A (N9830), Battle Mountain, NV, substantial damage. Probable cause: THE LOSS OF ENGINE POWER IN FLIGHT DUE TO A BROKEN NUMBER TWO ROCKER ARM. CONTRIBUTING TO THE ACCIDENT WAS THE VEHICLE ON THE ROAD WHICH RESULTED IN THE PILOT FLARING PREMATURELY.
- [NTSB FTW75FRD54](https://openairdocs.org/ntsb/FTW75FRD54), May 14, 1975: Grumman G-164A (N9830), Eunice, LA, substantial damage
- [NTSB CHI74FEA41](https://openairdocs.org/ntsb/CHI74FEA41), May 24, 1974: Grumman G-164A (N9830), Madison, IN, substantial damage

## FAA accident and incident reports on N9830 (4)

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [Accident 19950519014479A](https://openairdocs.org/incident/19950519014479A), May 19, 1995: Scwzer G164A (N9830), Colusa, CA, Substantial damage. Lost power on spray run. Made hard landing in flooded rice field. No engine defects found.
- [Accident 19890621016779A](https://openairdocs.org/incident/19890621016779A), Jun 21, 1989: Scwzer G164A (N9830), Battle Mountain, NV, Substantial damage. Engine quit. Tried to land on freeway. Pulled up,stalled,and crashed avoiding vehicles. Cylinder rocker arm failed.
- [Accident 19750519013499A](https://openairdocs.org/incident/19750519013499A), May 19, 1975: Gulstm G164C (N9830), Eunice, LA, Substantial damage. Hit rice levee
- [Accident 19740524018549A](https://openairdocs.org/incident/19740524018549A), May 24, 1974: Gulstm G164A (N9830), Madison, IN, Substantial damage. Factory rep chose to safety wire park brake out of sys. Undtmnd foreign substance btwn discs-flange

---
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.