From SKYbrary Wiki
| Summary
|
| On 5 July 2007, in daylight and good visibility, a Comair CRJ100 on an outbound scheduled service flight was cleared by a GND Controller to taxi across active runway 22 on which a Delta AL Boeing 737-800 also operating a scheduled service flight had already been cleared to land by the (TWR) local controller. The crossing to be made did not allow the CRJ100 crew to see up the runway towards the landing threshold until they had almost completed the crossing. When they did see the by then landed B738 coming towards them, they immediately increased thrust on the single operating engine to accelerate clear. The FAA account of the incident classified the incursion at low risk with a 3200 ft minimum separation between the two aircraft.
|
|
|
| Event Details
|
| When
|
July 2007
|
| Event Type
|
HF, RI
|
| Day/Night
|
Day
|
| Flight Conditions
|
On Ground - Normal Visibility
|
| General
|
| Tag(s)
|
ATC Training
Aircraft-aircraft near miss
|
| HF
|
| Tag(s)
|
Ineffective Monitoring
ATC Unit Co-ordination
ATC clearance error
|
| RI
|
| Tag(s)
|
ATC error
Incursion after Landing
Runway Crossing
Near Miss
|
| Safety Net Mitigations
|
| Malfunction of Relevant Safety Net
|
No
|
| A-SMGCS
|
Partially effective
|
| Outcome
|
| Damage or injury
|
No
|
| Aircraft damage
|
Nonewarning.png"None" is not in the list of possible values (Minor, Major, Hull loss) for this property.
|
| Injuries
|
Nonewarning.png"None" is not in the list of possible values (Few occupants, Many occupants, Most or all occupants) for this property.
|
| Fatalities
|
Nonewarning.png"None" is not in the list of possible values (Few occupants, Many occupants, Most or all occupants) for this property.
|
| Causal Factor Group(s)
|
| Group(s)
|
Air Traffic Management
|
| Safety Recommendation(s)
|
| Group(s)
|
None Made
|
| Investigation Type
|
| Type
|
Independent
|
Description
On 5 July 2007, in daylight and good visibility, a Comair CRJ100 on an outbound scheduled service flight was cleared by a GND Controller to taxi across active runway 22 on which a Delta AL Boeing 737-800 also operating a scheduled service flight had already been cleared to land by the (TWR) local controller. The crossing to be made did not allow the CRJ100 crew to see up the runway towards the landing threshold until they had almost completed the crossing. When they did see the by then landed B738 coming towards them, they immediately increased thrust on the single operating engine to accelerate clear. The FAA account of the incident classified the incursion at low risk with a 3200 ft minimum separation between the two aircraft.
The Investigation
An Investigation was carried out by the NTSB. Their Investigation found that the minimum separation recorded between the two aircraft was actually 600 feet and that the B738 had crossed the runway threshold some 6 seconds before the CRJ 100 entered the same runway to begin the crossing.
It also established that the Ground Controller involved had been under training with a qualified ground controller and had been authorised by the (TWR) local controller “via a conditional clearance, to taxi another aircraft across runway 22 after the aircraft in front of (the Delta B738) had passed taxiway F (the crossing taxiway being used by the Comair CRJ100) on the landing rollout. The (TWR) local controller then coordinated with the TWR Supervisor for the aircraft following the (Delta B738 to be removed from) the landing sequence because of insufficient separation. The ground controller mistakenly believed that (it was the Delta B738 which) was being taken out of the landing sequence and authorised (the CRJ100) to cross runway 22 without coordinating with the TWR local controller as required.”
Related Articles
Further Reading
