NYC02LA073 · Annis Fisher FP-202
Annis Fisher FP-202 · Accident: in flight collision with object during initial climb
From Parksley, VA (no airport) to Crisfield-Somerset County Airport (W41)
Event
- NTSB case
- NYC02LA073
- 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
Annis Fisher FP-202
- Aircraft type
- Annis FISHER FP-202
- 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
- N4348V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Parksley, VA (no airport)To Crisfield-Somerset County Airport (W41), Crisfield, MD
- 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
- Initial climb
- 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire, static
- 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 › Planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot completed the engine run up checks, and then taxied the homebuilt airplane onto the 1,100-foot grass runway. He advanced the throttle, and the engine responded normally. The pilot released the brakes, and the airplane started to accelerate. During the ground roll, the pilot noticed no change in engine noise or rpm, but felt the airplane was accelerating slower than normal, which he contributed to the fact it had rained the day before, making the ground soft and the grass wet. Even with the reduced acceleration, he felt he could safely continue the takeoff. The airplane lifted off about 2/3 down the runway, striking some power lines during the initial climb, and then impacted the ground. The pilot reported he experienced no preimpact failures or malfunctions with the airplane, and that the airplane normally utilizes 300 to 500 feet of runway before lifting off.
Probable cause
The pilot's decision to continue the takeoff. A factor in the accident was the soft wet runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC02LA073
- Event ID
- 20020326X00395
- Case number
- NYC02LA073
- 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: 283622139b037c5b5751caac216019a117079643d5842c58e43bd3040ece01f9; retrieved 2026-09-21T19:45:46.403Z.