 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Following a modest ground conflict between departing and taxiing aircraft on and/or crossing runway 15 at btv the ground controller discussed his belief that recent modifications to the intersecting runway 19 have contributed to increased frequency of such events.
| Attributes | |
| ACN | 1078125 |
| Time | |
| Date | 201304 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | BTV.Airport |
| State Reference | VT |
| Aircraft 1 | |
| Make Model Name | King Air C90 E90 |
| Flight Phase | Taxi |
| Route In Use | None |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Challenger 300 |
| Flight Phase | Taxi |
| Route In Use | None |
| Flight Plan | IFR |
| Person 1 | |
| Function | Ground Instructor |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Ground Incursion Taxiway |
Narrative:
While I was training a developmental on local control; ground control taxied out a king air requesting runway 19 via charlie/alpha.a crj-700 landed runway 15 and the developmental instructed him to turn right on bravo and hold short of runway 19. The developmental then instructed a CL30 to line up and wait on runway 15 and advising 'traffic crossing down field'.the developmental then cleared the king air to 'cross runway 15'. The king air then crossed the runway 15 hold short line and turned towards the runway 19 threshold; deviating from taxiway alpha. I pointed out to the developmental to 'watch the king air'. The developmental then instructed the king air to 'make a hard left and stay on alpha; then a right; hold short runway 19.' the king air was very confused but after some further direction cleared the runway 15/19 intersection. The developmental then cleared the CL30 to line up and wait for takeoff. When the btv airport administration created a 20 year master development plan they planned to extend runway 19 past runway 15 due to the confusion it caused for aircraft departing runway 19. Unfortunately; before the construction of the runway 19 extension occurred; the airport administration did not seriously confer with the airport users to explain that the extension would be in the form of only a displaced threshold of approximately 400 ft in length. There is absolutely no benefit to this runway extension. It; frankly; is a safety hazard that has been a contributing factor in many go-around's; unnecessary increased runway occupancy times; and aborted takeoffs. These occur on a very regular basis.the vast majority of aircraft that use runway 19 are small single or light twin engine aircraft that are capable of taking off and landing on runways shorter than runway 19. Runway 19 should have never been extended to mitigate confusion if the airport was truly interested in mitigating confusion then they should have shortened runway 19 as not to intersect runway 15. This would have left approximately 2;000 ft available; a sufficient amount for the aircraft currently using it. Although it is a; unrealistic recommendation I feel that runway 19 should be shortened.
Original NASA ASRS Text
Title: Following a modest ground conflict between departing and taxiing aircraft on and/or crossing Runway 15 at BTV the Ground Controller discussed his belief that recent modifications to the intersecting Runway 19 have contributed to increased frequency of such events.
Narrative: While I was training a Developmental on Local Control; Ground Control taxied out a King Air requesting Runway 19 via Charlie/Alpha.A CRJ-700 landed Runway 15 and the Developmental instructed him to turn right on Bravo and hold short of Runway 19. The developmental then instructed a CL30 to line up and wait on Runway 15 and advising 'traffic crossing down field'.The Developmental then cleared the King Air to 'cross Runway 15'. The King Air then crossed the Runway 15 hold short line and turned towards the Runway 19 threshold; deviating from Taxiway Alpha. I pointed out to the Developmental to 'watch the King Air'. The Developmental then instructed the King Air to 'make a hard left and stay on Alpha; then a right; hold short Runway 19.' the King Air was very confused but after some further direction cleared the runway 15/19 intersection. The Developmental then cleared the CL30 to line up and wait for takeoff. When the BTV airport administration created a 20 year master development plan they planned to extend Runway 19 past Runway 15 due to the confusion it caused for aircraft departing Runway 19. Unfortunately; before the construction of the Runway 19 extension occurred; the airport administration did not seriously confer with the airport users to explain that the extension would be in the form of only a displaced threshold of approximately 400 FT in length. There is absolutely no benefit to this runway extension. It; frankly; is a safety hazard that has been a contributing factor in many go-around's; unnecessary increased runway occupancy times; and aborted takeoffs. These occur on a very regular basis.The vast majority of aircraft that use Runway 19 are small single or light twin engine aircraft that are capable of taking off and landing on runways shorter than Runway 19. Runway 19 should have never been extended to mitigate confusion if the airport was truly interested in mitigating confusion then they should have shortened Runway 19 as not to intersect Runway 15. This would have left approximately 2;000 FT available; a sufficient amount for the aircraft currently using it. Although it is a; unrealistic recommendation I feel that Runway 19 should be shortened.
Data retrieved from NASA's ASRS site as of July 2013 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.