ERA14CA012 · Classic Aircraft Corp WACO YMF
Classic Aircraft Corp WACO YMF · Accident: loss of control on ground during landing
From Somerset Airport (SMQ) to Somerset Airport (SMQ)
Event
- NTSB case
- ERA14CA012
- 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
- Unknown
- 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
Classic Aircraft Corp WACO YMF
- Aircraft type
- Classic WACO YMF
- 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
- N62XX
- Operator
- Singh Meera
- Onboard fatalities
- Unknown
- Route
- From Somerset Airport (SMQ), Somerville, NJTo Somerset Airport (SMQ), Somerville, NJ
- Aircraft age
- About 24 years (built 1989)
- 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
- Landing · landing roll
- Defining eventThe 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
- Loss of control on ground
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that she departed from runway 26, and flew over a local golf course, then turned to return to the departure airport where she entered the traffic pattern on the downwind leg for runway 26, flying between 75 and 80 knots. She descended to 800 feet and prior to turning base leg she slowed to between 65 and 70 knots, which she maintained on base and final. She turned onto base leg and descended to 500 feet and at that altitude turned onto final approach for runway 26 slowing at touchdown. She performed a wheel landing a few feet farther along the runway than typical or "a little long" which she described as abeam the western edge of the hangars. The airplane travelled onto a portion of the runway that causes undulations and with aft stick applied after encountering the undulations, she tapped the brakes. The airplane then nosed over. She further reported that there was nothing mechanically wrong with the airplane that caused the nose over, and the area of the runway where the undulations were located also was not the cause of the accident.
Various video recordings depicted the approach and nose-over sequence; however, the actual touchdown point was not captured.
An individual at the accident airport provided a reference for where the airplane came to rest, which was located before a diagonal line that is visible in a Google Earth image.
Plotting on Google Earth of the pilot reported touchdown point indicates that position was located about 800 down the 2,200 foot long grass runway, which has the west 500 feet described as being unsuitable for takeoff or landing due to uneven surface. Therefore, the pilot reported touchdown point occurred nearly halfway down the usable length of runway. Although the exact location where the airplane came to rest was not documented, based on video recording, that was located about 500 feet from the pilot reported touchdown point.
Probable cause
The pilot's failure to maintain aircraft control while applying wheel brakes during landing roll resulting in the airplane nosing over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14CA012
- Event ID
- 20131022X22341
- Case number
- ERA14CA012
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 707218f8e271fe69b328b52618e7aa24b97718b4fe7ddf821edca16e6234cdee; retrieved 2026-09-15T22:59:50.265Z.