ASN Wikibase Occurrence # 176343
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Saturday 10 April 2004 |
| Time: | 09:59 |
| Type: |  Cirrus SR22 |
| Owner/operator: | Private |
| Registration: | N916LJ |
| MSN: | 0080 |
| Year of manufacture: | 2001 |
| Total airframe hrs: | 516 hours |
| Fatalities: | Fatalities: 0 / Occupants: 1 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | North Lauderdale, FL -
 United States of America
|
| Phase: | Approach |
| Nature: | Private |
| Departure airport: | Fort Lauderdale, FL (KFXE) |
| West Palm Beach, FL (KPBI) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The pilot reported no discrepancies either during the preflight inspection or during the engine run-up before takeoff. He obtained his IFR clearance, and shortly after takeoff the flight encountered IMC at 400 feet MSL. While climbing, the vertical speed indicator suddenly decreased to 0, then increased to 2,000 FPM, then went back to 0. Moments later the altimeter began bouncing with very large deflections, then the attitude indicator did not agree with the turn coordinator. He did not activate the alternate static source as per the pilot's operating handbook, and advised the controller that he was "losing gauges" and he would be unable to execute an instrument landing system approach to the departure airport. He activated the cirrus airframe parachute system (CAPS), and the airplane descended into trees. The pilot indicated he had 105 hours actual instrument flight time. Following recovery, the pilot's attitude indicator (AI) and turn coordinator (TC) powered up normally when battery No. 2 was switched on. Approximately 1 teaspoon of water was found between the static port openings and the alternate static air valve in the static lines. Testing of the water sample revealed it contained 3.2 mg/L of fluoride, which is common in tap water. The airplane's static system was tested to 1,000 feet, and the flight instruments were found to operate erratic. The vertical speed indicator fluctuated between 500 and 2,000 feet per minute, the altimeter indicated 200 feet, the airspeed indicated 60 knots (KTS), and the instruments did not return to zero when the pressure was returned to sea-level. When pressurizing the pitot line to 100 KTS the airspeed was found to be "sticky" and was "leaking" approximately 5 KTS per minute. Testing of the pitot static system from the alternate air source revealed no discrepancies. Bench testing of the attitude indicator and turn coordinator, revealed no discrepancies. Damage to the master control unit (MCU) occurred while trying to jump start the engine post-accident. No pilot reports (PIREP's) indicated any significant turbulence over Florida at the time of the accident. The engine was run on the airplane for approximately 10-15 minutes with no discrepancies noticed.
Probable Cause: The erratic operation of the pitot-static system associated flight instruments due to water contamination, and the pilot's failure to take the appropriate corrective actions.
Accident investigation:
 |
|
Sources:
NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20040426X00510&key=1
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 24-May-2015 12:27 | Noro | Added |
| 21-Dec-2016 19:30 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 07-Dec-2017 17:54 | ASN Update Bot | Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation