# Accident 20060630022169A: Aermer FALCOF8L, Montgomery, NY, June 30, 2006

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 30, 2006, 15:39 local time
- Place: Montgomery, NY
- Airport: Orange County Airport
- Damage: Destroyed
- Phase of flight: In Traffic Pattern-Circling
- Operating rules: General operating rules (Part 91)
- Location: 41.5097° N, 74.2644° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=41.5097&lon=-74.2644&mi=10
- Aircraft: N4TB, a cancelled registration (https://openairdocs.org/deregistered/N4TB-2007-11-01) (OpenAirDocs)
- Registry model: Baker Timothy C FALCO F8L (registry code 0566070, https://openairdocs.org/model/baker-timothy-c-falco-f8l) (OpenAirDocs)
- Registry engine: Lycoming IO-320 series (registry code 41509, https://openairdocs.org/engine/lycoming-io-320-series) (OpenAirDocs)
- Reported make and model: AERMER FALCOF8L
- Reported engine: LYC IO320*
- Fatal injuries: 0
- Pilot flight hours: 3,890 total, 481 in this make and model, 1 in the last 90 days
- NTSB investigation: [NTSB NYC06CA164](https://openairdocs.org/ntsb/NYC06CA164) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20060630022169A

## Narrative

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

(-23) AT 15:39E, N4TB, A FLACO F8L, DEPARTED FROM RUNWAY 26 AT MGJ AND REPORTED PROBLEMS WITH THE ENGINE. THE AIRCRAFT WAS RETURNING TO LAND ON RUNWAY 3, WHEN THE ENGINE STALLED. THE PILOT LANDED THE AIRCRAFT ON THE GRASS WITH UNKNOWN DAMAGES AND MINOR INJURY TO THE PILOT, THE SOLE OCCUPANT. A POST ACCIDENT REVIEW OF THE AIRCRAFT REVEALED IT IS DESTROYED. A REVIEW OF THE AIRCRAFT'S LOGBOOKS INDICATES THE LAST CONDITION INSPECTION TOOK PLACE ON 12/07/2002 WHEN THE AIRCRAFT TOTAL TIME WAS 740.2 HOURS. THE PILOT'S LAST THIRD CLASS MEDICAL TOOK PLACE ON SEPTEMBER 09, 2003. A CALL TO THE FAA MEDICAL BRANCH ON JULY 03, 2006 AT 09:10E, CONFIRMED THIS. THE PILOT'S LAST RECORDED BIANNUAL FLIGHT REVIEW IS LOGGED AS TAKEN PLACE ON SEPTEMBER 08, 2001. AT THE ACCIDENT SITE THE FORWARD FUEL TANK WAS OBSERVED TO CONTAIN 1 GALLON OR LESS OF LIQUID. THE CHECKLIST FOR THIS AIRCRAFT RECOVERED AT THE ACCIDENT SITE, STATES IN ITEM 5 OF THE BEFORE STARTING SECTION "FUEL - FORWARD TANK (TOTALIZER)." THE FUEL SELECTOR SWITCH AT THE ACCIDENT SITE WAS FOUND TO BE SOMEWHERE BETWEEN THE FRONT AND AFT TANKS.

## 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 NYC06CA164](https://openairdocs.org/ntsb/NYC06CA164), Jun 30, 2006: Baker, Timithy Falco F8L (N4TB), Montgomery, NY, substantial damage. Probable cause: The pilot's inadequate pre-flight inspection, which resulted in a loss of engine power due to fuel contamination.

## Other reports on N4TB (3)

Matched to the same aircraft by N-number and date.

- [Incident 20030425017039I](https://openairdocs.org/incident/20030425017039I), Apr 25, 2003: Aermer FALCOF8L (N4TB), Montgomery, NY, Minor damage. (-23) Pilot stated he lowered landing gear did not check gear, down light. Pilot landed aircraft with the landing gear in the up position.
- [Incident 19990102000139I](https://openairdocs.org/incident/19990102000139I), Jan 2, 1999: Amtr F8LFALCO (N4TB), Lincoln Park, NJ, Minor damage. Gear collapsed on landing. Landing gear down. Limit switch tab bent 1/32". Tab engages switch setting off green light-turning off motor prior to complete…
- [Incident 19960403013589I](https://openairdocs.org/incident/19960403013589I), Apr 3, 1996: Aermer FALCOF8L (N4TB), Cincinnati, OH, Minor damage. Narrative: on April 3, 1996 at 1330 an experimental aircraft, falco-8L landed at louisa county airport, louisa, Virginia. The pilot failed to lower the landing…

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.