# Accident 20000325004629A: Bbavia 11AC, Fort Leavenwort, KS, March 25, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 25, 2000, 17:30 local time
- Place: Fort Leavenwort, KS
- Airport: Sherman Aaf
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 39.3609° N, 94.9105° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=39.3609&lon=-94.9105&mi=10
- Aircraft: N9570E, registered now (https://openairdocs.org/aircraft/N9570E) (OpenAirDocs)
- Registry model: Aeronca 11AC (registry code 0191102, https://openairdocs.org/model/aeronca-11ac) (OpenAirDocs)
- Registry engine: Continental A&C65 series (registry code 17003, https://openairdocs.org/engine/continental-a-c65-series) (OpenAirDocs)
- Reported make and model: BBAVIA 11AC
- NTSB investigation: [NTSB CHI00LA099](https://openairdocs.org/ntsb/CHI00LA099) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000325004629A

## Narrative

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

(-23) N9570E WAS MAKING A SERIES OF TOUCH AND GO LANDINGS ON RUNWAY 15 AT FORT LEAVENWORTH, KANSAS (FLV). THE AIRPLANE TOUCHED DOWN AND JUST AS THE PILOT, MR. DISCHNER, PREPARED TO START THE TAKEOFF ROLL, HIS AIRPLANE WAS HIT FROM THE REAR BY N51993, CAUSING SUBSTANTIAL DAMAGE TO BOTH AIRCRAFT. N9570E DOES NOT HAVE AN ELECTRICAL SYSTEM AND THEREFORE NO RADIO COMMUNICATION.

## 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 CHI00LA099](https://openairdocs.org/ntsb/CHI00LA099), Mar 25, 2000: Aeronca 11AC (N9570E), Ft. Leavenworth, KS, substantial damage. Probable cause: the pilot of N51933 did not see and maintain clearance from N9570E. A factor associated with the accident was the pilot of N51933's restricted forward visibility during the landing due to the…

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.