# Accident 20030725022039A: Amtr ALARUSCH2T, Crystal River, FL, July 25, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 25, 2003, 14:40 local time
- Place: Crystal River, FL
- Airport: Homosassa Air Terminal Airport
- Damage: Substantial damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 28.8672° N, 82.5711° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=28.8672&lon=-82.5711&mi=10
- Aircraft: N643AM (not matched to a registry record)
- Reported make and model: AMTR ALARUSCH2T
- People aboard: 1
- Fatal injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 30 total, 30 in this make and model, 30 in the last 90 days
- NTSB investigation: [NTSB MIA03CA151](https://openairdocs.org/ntsb/MIA03CA151) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030725022039A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) ON JULY 25, 2003, AT 1440 EDT, A ALARUS CH-2T, N643AM, REGISTERED TO NATIONAL AVIATION HOLDINGS INC., RAN OFF THE RUNWAY ON LANDING AT CRYSTAL RIVER AIRPORT, CRYSTAL RIVER, FLORIDA, WHILE ON A STUDENT SOLO CROSS COUNTRY FLIGHT. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME AND A VFR FLIGHT PLAN WAS FILED. THE AIRCRAFT WAS SUBSTANTIALLY DAMAGED THE STUDENT PILOT WAS NOT INJURED. THE FLIGHT ORIGINATED AT ST. PETERSBURG, FLORIDA ON JULY 25, AT 1400 HOURS.

## The NTSB's investigation of this event (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 MIA03CA151](https://openairdocs.org/ntsb/MIA03CA151), Jul 25, 2003: Aircraft Mfg & Dev. CH2T (N643AM), Crystal River, FL, substantial damage. Probable cause: The student pilot 's failure to maintain control while landing in crosswind which resulted in airplane departing the runway and incurring damage.

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. For accidents, the NTSB's own investigation is the fuller record.

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