Plane with 164 aboard just 30m from midair collision at King Phalo Airport
A jet with 164 people on board came within 30m of disaster when a student pilot at the controls of a light aircraft mixed up “left” and right”.
A near-miss involving the two planes, which happened at King Phalo Airport in East London on August 25, emerged this week in an SA Civil Aviation Authority report.
The regulator launched an investigation after the pilot of a Safair Boeing 737 carrying six crew and 158 passengers from Cape Town reported a near collision when the plane was landing at 7.25am.
The preliminary serious incident report said an air traffic controller twice ordered the 33-year-old student pilot to turn right to avoid a collision with Safair 142, but he turned left instead and came within 30m of the jet.
The pilot, identified in the report as a Ghanaian with “expert” English skills, was on a solo navigational training flight from Port Alfred in a four-seater Piper Cherokee owned by 43 Air School.
In the sober words of the CAA investigator, the pilot's “deviation from instructions led to loss of separation between the aircraft”.
He added: “Later, Safair 142 (ZS-JRE) landed safely and vacated the runway. Prima 285 [the student pilot's call sign] conducted one touch-and-go landing, reported safely airborne and routed outbound via Kayser’s Beach.
“No injuries resulted from this serious incident and neither aircraft sustained damage.”
An “air proximity” incident is defined as any circumstance where the degree of separation between two aircraft is considered by either pilot to have constituted a hazardous situation involving potential risk of collision.
The Safair jet would have been flying at around 250km/h when the student pilot passed about 30m directly overhead as the jet made its final approach at around 132m above the ground.
The investigation report said: “Prima 285 was inbound from the north and requested to conduct two touch-and-go landings.”
Air traffic control (ATC) instructed the pilot to go ahead, but at 7.21:48 the Safair pilot reported that his jet was established on the instrument landing system for a landing.
“ATC instructed them to continue with approach. At 7.22:10, Prima 285 was instructed by ATC to turn right and to continue routing north of the aerodrome and to stand by for further instructions; this was to keep the aircraft clear from the final approach path.
“At 7.23:47, ATC instructed Prima 285 to turn right and re-establish on the left downwind for Runway 11. However, the pilot did not read back the ATC instructions correctly; instead of turning right, he turned left towards final approach path of Runway 11.
“At 7.24:28, ATC cleared Safair 142 to land. At 7.25:12, Safair 142 enquired from ATC if he was aware of traffic ... in front of them.
“At 7.25:27, ATC instructed the pilot of Prima 285 to turn right. At 7.25:35, ATC again instructed the pilot of Prima 285 to turn right immediately, this time with a much more forceful tone. However, the pilot continued with the left turn.
“Safair 142 was advised of the instructions issued to Prima 285 and to continue to land as both aircraft were in sight and Prima 285 was higher.
“Prima 285 flew overhead Safair 142 and the pilot was instructed to orbit and then to report established on final approach for Runway 11. At this time, Safair 142 had landed and vacated the runway.”
The student pilot had 104 hours' flying experience, according to the CAA report, compared with a total of 14,375 hours between the 32-year-old Safair pilot and his 37-year-old co-pilot.
The CAA report said its purpose was not to apportion blame. It added, however: “The ATC recordings and radar files were made available for this investigation.
“Throughout communication between [East London] ATC and both aircraft, there were clear instructions from ATC and correct read-back by the flight officer of Safair 142.
“However, the pilot of Prima 258 did not read back the ATC instructions correctly at some point during communication.”
Would you like to comment on this article or view other readers' comments? Register (it’s quick and free) or sign in now.
Please read our Comment Policy before commenting.