“The simulator session also identified a period of about two minutes between about 2800ft and 1000ft in the descent where no control manipulations or systems activation was recorded," the report said.
“In contrast, during that period, a number of tasks should have normally been completed in preparation for landing.”
These actions include putting the landing great down (which was still not deployed at under 500ft), selecting the auto brake and changing the configuration of the flaps.
It is likely that the first officer’s performance was “adversely affected by fatigue", while the captain did not appropriately monitor his actions or the aircraft's configuration.
Read more:
Texting captain sparks Jetstar flight drama | News.com.au