37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1531788 |
Time | |
Date | 201804 |
Local Time Of Day | 0601-1200 |
Aircraft 1 | |
Make Model Name | SR22 |
Operating Under FAR Part | Part 91 |
Flight Phase | Parked |
Flight Plan | None |
Component | |
Aircraft Component | Position Computing System |
Person 1 | |
Function | Single Pilot |
Qualification | Flight Crew Instrument Flight Crew Commercial |
Experience | Flight Crew Last 90 Days 100 Flight Crew Total 620 Flight Crew Type 270 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural FAR Deviation - Procedural Maintenance |
Narrative:
Aircraft was equipped with adsb (automatic dependent surveillance broadcast) out using an apparently mis-configured setup causing adsb to transmit a signal in violation of far 91.227. Checks by the avionics installer as well as independent avionics specialists have failed to fix the issue. In talking with the FSDO; I realized that the airplane was in violation of the far covering adsb installations during the past year; over three hundred flights have occurred with incorrect adsb settings. The current solution has been to disable adsb out from the gtx 330ES transponder until a permanent solution with proper configurations has been determined. I believe the tools avionics technicians use to verify the adsb solution are not working correctly as I have been told by multiple technicians that the adsb has been configured correctly and should work; yet tests from the FAA disagree. As a pilot and owner I find this frustrating since it seems the avionics techs and the FAA have a different methods of determining adsb accuracy and integrity.
Original NASA ASRS Text
Title: Cirrus SR22 pilot reported an ADSB (Automatic Dependent Surveillance Broadcast) configuration issue.
Narrative: Aircraft was equipped with ADSB (Automatic Dependent Surveillance Broadcast) out using an apparently mis-configured setup causing ADSB to transmit a signal in violation of FAR 91.227. Checks by the avionics installer as well as independent avionics specialists have failed to fix the issue. In talking with the FSDO; I realized that the airplane was in violation of the FAR covering ADSB installations during the past year; over three hundred flights have occurred with incorrect ADSB settings. The current solution has been to disable ADSB out from the GTX 330ES transponder until a permanent solution with proper configurations has been determined. I believe the tools avionics technicians use to verify the ADSB solution are not working correctly as I have been told by multiple technicians that the ADSB has been configured correctly and should work; yet tests from the FAA disagree. As a pilot and owner I find this frustrating since it seems the avionics techs and the FAA have a different methods of determining ADSB accuracy and integrity.
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.