# N6633K: not currently registered

- Registered now: No (not in the FAA registry file). The mark may be reserved or free to assign
- Earlier aircraft: 2
- Last cancelled: April 30, 2025
- FAA registry: https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=6633K
- Page: https://openairdocs.org/aircraft/N6633K

## Aircraft that carried N6633K

- [Cancelled 2025-04-30](https://openairdocs.org/deregistered/N6633K-2025-04-30): Grumman Acft ENG Cor-Schweizer G-164B, S/N 400B. N-number assigned, not yet registered
- [Cancelled 1960-11-17](https://openairdocs.org/deregistered/N6633K-1960-11-17): Republic RC-3, S/N 906. Exported to Canada. Owner: [Cawley William E](https://openairdocs.org/faa-owner/CAWLEY%20WILLIAM%20E), [Richland, WA](https://openairdocs.org/faa-place/WA/Richland)

## NTSB investigations on N6633K (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 WPR24LA282](https://openairdocs.org/ntsb/WPR24LA282), Aug 13, 2024: Grumman Acft ENG Cor-Schweizer G-164B (N6633K), Durham, CA, substantial damage. Probable cause: The pilot’s failure to maintain clearance from powerlines, which resulted in a wire strike.
- [NTSB CHI99LA215](https://openairdocs.org/ntsb/CHI99LA215), Jul 3, 1999: Grumman-Schweizer G-164B (N6633K), Page, ND, substantial damage. Probable cause: the pilot's failure to compensate for the wind conditions. Factors were the sudden windshift and the crops.
- [NTSB CHI97LA204](https://openairdocs.org/ntsb/CHI97LA204), Jul 7, 1997: Grumman-Schweizer G-164B (N6633K), Donnelly, MN, substantial damage. Probable cause: undetermined event resulting in the broken connecting rod and cylinder.
- [NTSB LAX91LA301](https://openairdocs.org/ntsb/LAX91LA301), Jul 9, 1991: Grumman G-164B (N6633K), Eloy, AZ, substantial damage. Probable cause: THE FAILURE OF THE PILOT TO MAINTAIN THE TERRAIN CLEARANCE OF THE AIRCRAFT WHILE MANEUVERING FOR A POTENTIAL EMERGENCY LANDING ON A MOONLESS DARK NIGHT.

## FAA accident and incident reports on N6633K (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 20240813017999A](https://openairdocs.org/incident/20240813017999A), Aug 13, 2024: Grumman Acft Eng Cor-Schweizer G-164B (N6633K), Durham, CA, Substantial damage. The pilot reported that while maneuvering under a power line he started to bank the aircraft before he was clear of the line which seperated most of the…
- [Accident 19990703046169A](https://openairdocs.org/incident/19990703046169A), Jul 3, 1999: Scwzer G164B (N6633K), Page, ND, No damage. (-23) On July 3, 1999 at 0730 local time a Grumman G-164 registered to tall towers aviation inc was damaged during takeoff fro an aerial application flight.…
- [Incident 19970706021209I](https://openairdocs.org/incident/19970706021209I), Jul 6, 1997: Scwzer G164B (N6633K), Donnelly, MN, Minor damage. During turn around lost power. Oil on windshield. Hard landing on road. Folded left main gear. Threw rod thru case. (-23) pilot was making turn for spray run &…
- [Accident 19910708026729A](https://openairdocs.org/incident/19910708026729A), Jul 8, 1991: Scwzer G164B (N6633K), Eloy, AZ, Substantial damage. Reported appealed engine lacked power on climbout. Hit ground and cartwheeled off end runway. Dark no ground lights

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