Piper PA-28R-200 N4499T
14 November 2009 · Dennisville, New Jersey, United States · Fatal
Summary
On 14 November 2009 at about 15:50 local time, a Piper PA-28R-200 registered N4499T was involved in an accident near Dennisville, New Jersey, United States. 2 people were on board and 2 died. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 15:50
- Classification
- Accident
- Location
- Dennisville, New Jersey, United States
- Nearest airport
- Woodbine Municipal Airport (OBI)
- Coordinates
- 39.2181, -74.7903
- Aircraft
- Piper PA-28R-200
- Registration
- N4499T
- Category
- Airplane
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Woodbine → Bloomington
- Aircraft damage
- Substantial
- Weather
- IMC
- Light
- Day
- NTSB number
- ERA10FA062
People
2 people died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 2 | 2 | 0 | 0 | 0 |
Probable cause
The non-instrument-rated pilot's decision to depart into known instrument meteorological conditions, which resulted in his spatial disorientation and overcontrol of the airplane and the subsequent in-flight structural failure. Contributing to the accident was the pilot's failure to use all available resources, including the autopilot and the air traffic controller.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
The non-instrument-rated private pilot/owner of the airplane had longstanding arrangements for the trip to his destination, which was about 500 miles east of where he lived and based his airplane. He originally planned to depart on Thursday morning, but instrument meteorological conditions (IMC) at the airport prevented him from leaving on Thursday or Friday. On Saturday morning, IMC still prevailed. Several witnesses observed the pilot and his son at the fuel dock, and all assumed that he would then taxi back to his hangar since the ceilings were between 200 and 400 feet above ground level. Instead, the airplane departed and disappeared from view into the overcast clouds. The pilot initially squawked the visual flight rules (VFR) code of 1200 on his transponder, but then contacted an air traffic controller for flight advisories. The controller assigned a discrete transponder code, and instructed the pilot to maintain VFR. For the next 7 minutes, multiple witnesses on and near the airport heard the airplane in their vicinity. All reported that it sounded like the airplane was continuously changing speed, direction, or both. Several witnesses then heard the airplane impact the ground. Airplane components were found in two locations: at the main wreckage site and along a debris path that consisted of the outboard portions of the left wing and left stabilator. Physical evidence indicated that the wing failed in the positive direction due to airloads and not due to any preseparation mechanical deficiencies. No other evidence of any preimpact component deficiencies or failures was discovered and examination of the wreckage and ground scars indicated that the engine was developing power at impact. Discussions with the pilot's wife revealed that he occasionally flew into or through clouds, albeit usually for short durations, in order to begin or complete his flights. In the case of the accident flight, the pilot had already delayed his departure 2 days, so he was highly motivated to begin the trip. Although the departure airport conditions were IMC, the pilot was aware that the forecast called for improved conditions towards his destination. In addition to his prior VFR operations into IMC, he did not hold a valid medical certificate and no current record of a required transponder inspection was located. Ground-based radar and onboard global positioning system (GPS) data revealed that the airplane flew a ground track that included about eight 360-degree turns and three 180-degree turns, and that its altitude varied continuously between 200 feet and 1,600 feet above mean sea level. The GPS and radar data clearly indicated that the pilot became disoriented and was unable to methodically and safely extract himself from his predicament. FAA guidance regarding VFR flight into IMC cautioned pilots to minimize attitude changes and obtain appropriate assistance, including use of the autopilot.
Quoted verbatim from the NTSB record.
Other Piper PA-28R accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 14 Jul 2009 | Piper PA-28R-180 | Tucson, Arizona, United States | New Mexico Flying Eagle Inc. | No injuries | - |
| 28 Feb 2009 | Piper PA-28R-200 | Fallbrook, California, United States | M.Y. Air Corp | No injuries | - |
| 23 Apr 2009 | Piper PA-28R-200 | Hilliard, Florida, United States | Garrison Chadrick | No injuries | - |
| 3 Dec 2009 | Piper PA-28R-200 | Nogales, Arizona, United States | Tiffin Aviation Service | No injuries | - |
| 14 Jun 2009 | Piper PA-28R-180 | Scotia, New York, United States | Kolath Airlines LLC | Fatal | 3 |
| 26 Aug 2009 | Piper PA-28R-201 | Luray, Virginia, United States | Aviation Adventures | No injuries | - |
All 1,342 records for this type
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 8 Jun 2009 | Taylorcraft BC12-D | Somerville, New Jersey, United States | - | No injuries | - |
| 25 Aug 2009 | Cessna 172RG | Rockaway, New Jersey, United States | Air Fleet Training Systems | Minor injuries | - |
| 19 Jul 2009 | Cessna 170B | Mahwah, New Jersey, United States | Ganim Rose B | Serious injuries | - |
| 9 Mar 2009 | Piper PA-42 | Belmar, New Jersey, United States | Hortmont Aviation Services Inc | No injuries | - |
| 7 Mar 2009 | Grumman TBM-3 | Millville, New Jersey, United States | Claire Aviation | Serious injuries | - |
| 5 Mar 2009 | Diamond DA 20-C1 | Morristown, New Jersey, United States | Robert Haddow | No injuries | - |