NYC07FA088 · Piper PA-28-151
Piper PA-28-151 · Accident: loss of control in flight on approach
From Monmouth Executive Airport (BLM) to Muñoz Landing Airstrip (BLM)
Event
- NTSB case
- NYC07FA088
- 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
- 1 · 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
Piper PA-28-151
- Aircraft type
- Piper PA-28
- 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
- N33521
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Monmouth Executive Airport (BLM), Farmingdale, NJTo Muñoz Landing Airstrip (BLM)
- 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
- Approach
- 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
- Loss of control in flight
- 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
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Physical impairment(stroke)
- Pilot in command › Planning/decision, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was conducting a local flight in good weather, when he radioed air traffic control (ATC), to request a vector to his home airport. At the time, the airplane was about 10 miles southwest of the home airport, heading away from the airport, and the pilot was lost and disoriented. The controller provided the pilot with a position report and a vector to the pilot's airport; however, the pilot subsequently flew erratically at low altitudes and did not respond to calls by ATC several times. The airplane then impacted a wooded area. The pilot had a history of multiple severe medical conditions, and was at high risk for a stroke, having had a previous transient ischemic attack (TIA) (mini-stroke). A TIA or stroke could reasonably account for the pilot's disorientation and confusion just prior to the accident. Although the autopsy did not discover any evidence of stroke, such evidence would only be seen if the pilot had a completed stroke and lived long enough for changes in the brain to become apparent (usually several hours at the least). It is most likely that the pilot's disorientation and confusion immediately prior to the accident were consistent with a stroke or a transient ischemic attack. None of the pilot's severe medical conditions or the medications he was taking was reported to the FAA during the pilot's most recent application for a third class medical certificate. Had they been reported, the certificate would have been denied. The pilot's personal physician believed that the pilot had not been flying as a pilot for at least 5 years. Examination of the wreckage did not reveal any preimpact mechanical malfunctions.
Probable cause
The pilot's improper decision to attempt a flight with known serious medical conditions, which resulted in impairment during cruise flight, likely due to a stroke or transient ischemic attack. A factor was the pilot providing false information on his medical application.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC07FA088
- Event ID
- 20070405X00372
- Case number
- NYC07FA088
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2007-03-29.
- API snapshot SHA-256: d467d3887af14aec4b4c9579c5a0c60f10084071e0779ebd3370a7263b247747; retrieved 2026-09-20T16:46:37.643Z.