|
Post by a380admirer on Apr 4, 2017 8:00:05 GMT 1
|
|
backstroke
delivered!
Just an aerospace engineer with thirst for knowledge
Posts: 1,913
|
Post by backstroke on Apr 5, 2017 7:18:11 GMT 1
|
|
|
Post by Shadow123 on Apr 5, 2017 8:42:14 GMT 1
|
|
backstroke
delivered!
Just an aerospace engineer with thirst for knowledge
Posts: 1,913
|
Post by backstroke on Apr 6, 2017 9:06:32 GMT 1
|
|
|
Post by bebertmallet on Apr 6, 2017 10:49:55 GMT 1
Preparation for the first flight ? Did we miss the rto ?
|
|
backstroke
delivered!
Just an aerospace engineer with thirst for knowledge
Posts: 1,913
|
Post by backstroke on Apr 6, 2017 11:14:01 GMT 1
Preparation for the first flight ? Did we miss the rto ? I don't know, that callsign change (now it is: www.flightradar24.com/FWZGC/cf6dfbc) a bit after, but so far there was no movement
|
|
backstroke
delivered!
Just an aerospace engineer with thirst for knowledge
Posts: 1,913
|
Post by backstroke on Apr 7, 2017 9:53:37 GMT 1
|
|
backstroke
delivered!
Just an aerospace engineer with thirst for knowledge
Posts: 1,913
|
Post by backstroke on Apr 7, 2017 12:24:54 GMT 1
Based on the movement chart entering the runway, is it possible that it was an RTO??
|
|
|
Post by a380admirer on Apr 7, 2017 13:02:17 GMT 1
Based on the movement chart entering the runway, is it possible that it was an RTO?? From the information from flightradar24 the maximum speed was 42 kts. Normaly that is to slow for an normal RTO. Maybe the recording was incorrect or there was any problem during the RTO. I have seen a similar case before and one day after the "smal" RTO the normal RTO was following.
|
|
|
Post by Shadow123 on Apr 10, 2017 9:41:16 GMT 1
|
|