Originally Posted by
Prada
A0283,
I was going through FR24 data once again. Look here:
Crash of Metrojet Flight 7K9268 | Flightradar24 Blog
It looks like after initial event plane lost yaw control. - tail fin was lost or gaping hole created in fuselage creating non symmetric drag, or both
with plane loosing yaw control, static ports might become not as static as required for correct flight level indication. Due to abnormal attitude against airflow.
I wonder which ADIRU data was fed to ADS-B? Captain side? Then we can tell yaw attitude via abrupt flightlevel changes. Compared to GPS data.
i have extracted these figs from your link in your post
04:13:03 KGL9268 30.157 34.174 30650 296 332 -5696 32000
04:13:08 KGL9268 30.161 34.173 30825 246
351 4544 32000
04:13:11 KGL9268 30.177 34.162 29925 306 325 -6080 32000
04:13:11 KGL9268 30.177 34.162 29925 306 325 -6080 32000
04:13:12 KGL9268 30.179 34.161 29925 184 350 -4352
at 04.13.08 it suddenly changes heading by 19 deg clockwise, 3 sec later it has swung 26 deg back anti clock. and 1 sec later it has swung 25 deg clockwise
If those yaw figures and rates are correct would the VS withstand that?