37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1581659 |
Time | |
Date | 201809 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | PA-32 Cherokee Six/Lance/Saratoga/6X |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | Direct |
Flight Plan | IFR |
Component | |
Aircraft Component | Electrical Power |
Person 1 | |
Function | Instructor Pilot Flying |
Qualification | Flight Crew Commercial Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 200 Flight Crew Total 450 |
Events | |
Anomaly | Aircraft Equipment Problem Critical |
Narrative:
During flight to ZZZ from home airport; the aircraft GPS failed. Quickly followed by a complete failure in the garmin 530. Approximately 3 minutes after this occurrence; the aircraft's pfd display showed a failure in all integrated equipment including attitude information; airspeed indicator; altimeter; heading indicator; and the integrated compass. Immediately following was a red and white flickering over the screen signaling what was presumed to be power failing to the display. During this time the pilot was attempting contact with center; of which no contact could be confirmed. At this time the pilot entered 7600 into transponder to signal lost communication. The pilot attempted to contact TRACON by telephone; though spotty service made attempts difficult. The best attempt was during flight nearby ZZZ1; where the pilot was able to inform TRACON that communications were lost and confirm continuing flight to ZZZ with an expected landing on runway xx; communication by phone was lost or failed at this point. None of the aircraft's lighting was operational including all exterior and interior lights. Cell phones were used to produce lighting for round dial gauges during flight as sunlight was diminishing. An mfd tablet running on standby power assisted limited navigation support while the pilot used tablet for primary GPS position; speed; and altitude enroute to ZZZ. The tablets were cross referenced with round dial instruments to ensure accuracy; though tablets were used mostly for convenience sake; (lighting and information organization). In this process the pilot noticed the ammeter indicating '0' amps; leading to the assumption of either an alternator failure and/or battery failure as the main cause. Around this time the transponder squawk code disappeared; though the backlight stayed lit up. Transponder functionality was unsure at this point. As the aircraft approached ZZZ; a diversion left of course was made to remain VFR as a descent to the airfield was made. Upon reaching the airfield the pilot maneuvered for a right downwind for runway xx; executed a wonderful landing; and taxiing to the parking area beneath the control tower led by light gun signals. The aircraft has had a previous battery issue within the past several weeks; to best of pilot knowledge; where the battery was recharged but not replaced. Information was provided to pilot by aircraft owner morning after incident surrounding this report.
Original NASA ASRS Text
Title: PA-32 pilot reported an electrical failure affecting multiple systems.
Narrative: During flight to ZZZ from home airport; the aircraft GPS failed. Quickly followed by a complete failure in the Garmin 530. Approximately 3 minutes after this occurrence; the aircraft's PFD display showed a failure in all integrated equipment including attitude information; airspeed indicator; altimeter; heading indicator; and the integrated compass. Immediately following was a red and white flickering over the screen signaling what was presumed to be power failing to the display. During this time the pilot was attempting contact with Center; of which no contact could be confirmed. At this time the pilot entered 7600 into transponder to signal lost communication. The pilot attempted to contact TRACON by telephone; though spotty service made attempts difficult. The best attempt was during flight nearby ZZZ1; where the pilot was able to inform TRACON that communications were lost and confirm continuing flight to ZZZ with an expected landing on runway XX; communication by phone was lost or failed at this point. None of the aircraft's lighting was operational including all exterior and interior lights. Cell phones were used to produce lighting for round dial gauges during flight as sunlight was diminishing. An MFD tablet running on standby power assisted limited navigation support while the pilot used tablet for primary GPS position; speed; and altitude enroute to ZZZ. The tablets were cross referenced with round dial instruments to ensure accuracy; though tablets were used mostly for convenience sake; (lighting and information organization). In this process the pilot noticed the ammeter indicating '0' amps; leading to the assumption of either an alternator failure and/or battery failure as the main cause. Around this time the transponder squawk code disappeared; though the backlight stayed lit up. Transponder functionality was unsure at this point. As the aircraft approached ZZZ; a diversion left of course was made to remain VFR as a descent to the airfield was made. Upon reaching the airfield the pilot maneuvered for a right downwind for runway XX; executed a wonderful landing; and taxiing to the parking area beneath the control tower led by light gun signals. The aircraft has had a previous battery issue within the past several weeks; to best of pilot knowledge; where the battery was recharged but not replaced. Information was provided to pilot by aircraft owner morning after incident surrounding this report.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.