# Accident 20001015039069A: Amtr SA300, Erwinna, PA, October 15, 2000 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: October 15, 2000, 17:48 local time - Place: Erwinna, PA - Airport: Vansant Airport - Damage: Substantial damage - Phase of flight: Forced/Precautionary Landing - Operating rules: General operating rules (Part 91) - Location: 40.4902° N, 75.0797° W: From the FAA, an estimate near the named town, within about 3 miles - Nearby events: https://openairdocs.org/map.md?lat=40.4902&lon=-75.0797&mi=10 - Aircraft: N3168, a cancelled registration (https://openairdocs.org/deregistered/N3168-2012-09-27) (OpenAirDocs) - Registry model: Starduster SA-300 (registry code 86601MR, https://openairdocs.org/model/starduster-sa-300) (OpenAirDocs) - Registry engine: Lycoming 0-435 (registry code 41516, https://openairdocs.org/engine/lycoming-0-435) (OpenAirDocs) - Reported make and model: AMTR SA300 - Reported engine: LYC O435 - Fatal injuries: 0 - Pilot flight hours: 2,426 total, 39 in this make and model, 39 in the last 90 days - NTSB investigation: [NTSB NYC01LA015](https://openairdocs.org/ntsb/NYC01LA015) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20001015039069A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (-23) PILOT DEPARTED RUNWAY 7 AT VAN SANT AIRPORT (9N1) AIRCRAFT ENGINE WAS RUNNING FINE ON INITIAL CLIMB OUT AND THEN IT SUDDENLY STOPPED RUNNING. PILOT LANDED STRAIGHT AHEAD IN A FIELD, CAUSING EXTENSIVE DAMAGE TO THE A/C.(.4)ON OCTOBER 15, 2000, ABOUT 1748 EASTERN DAYLIGHT TIME, A STARDUSTER SA-300, AN AMATEUR BUILT AIRPLANE, N3168, WAS SUBSTANTIALLY DAMAGED DURING A FORCED LANDING AFTER TAKEOFF FROM THE VANSANT AIRPORT (9N1), ERWINNA, PENNSYLVANIA. THE PILOT WAS SERIOUSLY INJURED. VISUAL METEOROLOGICAL CONDITIONS PREVAILED, AND NO FLIGHT PLAN WAS FILED FOR THE PERSONAL FLIGHT CONDUCTED UNDER 14 CFR PART 91. THE PILOT STATED THAT HE INTENDED TO RETURN TO HIS HOME AIRPORT, SKY MANOR AIRPORT, PITTSTOWN, NEW JERSEY. HE COMPLETED A PREFLIGHT INSPECTION OF THE AIRPLANE, AND PERFORMED A RUN-UP PRIOR TO DEPARTURE. AFTER DEPARTING 9N1, ABOUT 1/4 MILE FROM THE AIRPORT, THE ENGINE LOST ALL POWER. THE PILOT PERFORMED A FORCED LANDING INTO TREES, AND DID NOT RECALL ANY EVENTS AFTER THE IMPACT. THE PILOT ADDED THAT HE FLEW THE AIRPLANE EARLIER IN THE DAY, AND DID NOT EXPERIENCE ANY PROBLEMS. HE FURTHER STATED THAT THE AIRPLANE HAD TWO FUEL TANKS, THE CENTER AND MAIN TANK. THE FUEL SELECTOR HAD FOUR POSITIONS, "OFF," "TOP," "MAIN," AND "ACRO." THE PILOT DEPARTED WITH THE FUEL SELECTOR IN THE "ACRO" POSITION, WHICH DRAINED FROM THE LOWEST POINT IN THE MAIN TANK. THE MAIN TANK HAD APPROXIMATELY 12 GALLONS OF FUEL AT THE TIME OF DEPARTURE. A FEDERAL AVIATION ADMINISTRATION INSPECTOR EXAMINED THE ENGINE. HE ROTATED THE PROPELLER AND CONFIRMED CAMSHAFT AND CRANKSHAFT CONTINUITY. HE WAS NOT ABLE TO ATTAIN THUMB COMPRESSION ON THE NUMBER THREE AND NUMBER FIVE CYLINDERS. THE INSPECTOR STATED THAT THE NUMBER THREE CYLINDER HAD IMPACT DAMAGE, BUT HE DID NOT KNOW WHY THUMB COMPRESSION COULD NOT BE ATTAINED ON THE NUMBER FIVE CYLINDER. DUE TO IMPACT DAMAGE, THE INSPECTOR WAS UNABLE TO ACCESS THE MAGNETOS. THE INSPECTOR ADDED THAT FUEL WAS PRESENT IN THE CARBURETOR, AND HE DID NOT OBSERVE ANY FUEL CONTAMINATION. HE NOTED THAT THE FUEL SELECTOR WAS IN THE "OFF" POSITION, BUT EMERGENCY PERSONNEL STATED THAT THEY MOVED THE SELECTOR TO THE "OFF" POSITION. SEVERAL MONTHS LATER, THE PILOT PERFORMED A CURSORY EXAMINATION ON THE ENGINE. THE PILOT STATED THAT HE DID NOT FIND ANY DISCREPANCIES WITH THE ENGINE. HE ADDED THAT THE ENGINE WAS ORIGINALLY MANUFACTURED IN 1943. THE ENGINE WAS LAST OVERHAULED IN 1983. IT HAD 99 HOURS OF OPERATION SINCE THAT LAST OVERHAUL. ## 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 NYC01LA015](https://openairdocs.org/ntsb/NYC01LA015), Oct 15, 2000: Moore Starduster SA-300 (N3168), Erwinna, PA, substantial damage. Probable cause: A total loss of engine power during initial climb for undetermined reasons. ## Other reports on N3168 (1) Matched to the same aircraft by N-number and date. - [Accident 19840512018309A](https://openairdocs.org/incident/19840512018309A), May 12, 1984: Amtrso STARDUSTER2 (N3168), El Paso, TX, Substantial damage. Engine quit in the pattern. Struck a sand dune short of the runway. Pilot reported he was having fuel pump problems 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.