NYC85LA248 · Grumman American AA-1B
Grumman American AA-1B · Accident: total loss of engine power (non-mechanical) while maneuvering
From 34D · Orchard Park, NY to an unrecorded destination
Event
- NTSB case
- NYC85LA248
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Grumman American AA-1B
- Aircraft type
- Grumman American AA-1
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N2640R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 34D · Orchard Park, NYTo not recorded
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Maneuvering
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Total loss of engine power (non-mechanical)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Carburetor heat, improper use of
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT STATED THAT HE STARTED A MANEUVER AT 2700 FT. THE MANEUVER WAS A DIVE AFTER REDUCING PWR FOLLOWED BY A CLIMB WITH A LEFT TURN AT THE TOP FOLLOWED BY A DESCENDING LEFT TURN. THE TURN 'AT THE TOP' WAS UNCOORDINATED AND G FORCES OCCURRED. THROTTLE ADVANCEMENT AFTER THE MANEUVER PRODUCED NO ENG RESPONSE. A FIELD WAS SELECTED FOR A FORCED LNDG WHILE APPLYING CARBURETOR HEAT,AUX FUEL PUMP,RICH MIXTURE AND SWITCHING FUEL TANKS. THE PLT SAID 7 GALS OF FUEL REMAINED ABOARD. PWR IMPROVED AS THE ACFT NEARED THE GROUND. THE PLT ELECTED TO CONTINUE THE LNDG EVEN THOUGH THE FIELD WAS HEAVILY FURROWED. THE ACFT NOSED OVER AFTER LANDING. POST ACC INVEST REVEALED NO EVIDENCE OF MALFUNCTION. WEATHER CONDITIONS WERE FAVORABLE TO CARBURETOR/INDUCTION ICING.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC85LA248
- Event ID
- 20001214X37893
- Case number
- NYC85LA248
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 81a82b9b4f85ec0270a6e7cb76f6e71ebecdfd901dd4e42b4d7b23b39ed9a89a; retrieved 2026-09-22T01:39:31.118Z.