Squawk incorrect standby upon landing
Log:
15:42:06: Touchdown heading: 313 degrees
15:42:06: CG: 23.7%
15:42:06: NAV1: 117.30 (140°)
15:42:09: Spoilers deployed
15:42:39: Transponder was standby during LANDING (0.0)
15:42:41: Flaps 0 - 37 knots
15:43:05: --- Taxi ---
15:43:05: Flight time end
Transponder was incorrectly considered to be standby upon landing as the fokker sets it automatically. Apparently it sets the transponder to standby after 30 sec after landing or so, maybe it is speed related.
Offered solution: squawk shall not be checked from flare until taxiing.
Change History
(6)
| Milestone: |
→ General availability
|
| Status: |
accepted → implemented
|
| Status: |
implemented → delivered
|
| Resolution: |
→ implemented
|
| Status: |
delivered → closed
|
Changed the default transponder checking to use the the condition value!=1 instead of value==0. This might solve transponder check problems for this type.