37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1103107 |
Time | |
Date | 201307 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | PNS.Airport |
State Reference | FL |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Landing |
Route In Use | Vectors Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Instructor |
Qualification | Flight Crew Flight Instructor Flight Crew Commercial |
Experience | Flight Crew Last 90 Days 53 Flight Crew Total 3776 Flight Crew Type 3000 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict |
Narrative:
Primary runway in use was runway 8. We (C-172 in closed traffic) were cleared for low approach #2 following air carrier on straight in approach/landing on runway 8. An air carrier had been cleared for landing several miles north of the airport on runway 17. At least 3 skyhawks were in close traffic for runway 8 and 2 air carriers were holding short runway 17. During our approach to runway 8 and near/past the threshold the air carrier executed a go around runway 17 and we executed steep left climbing turn following tower instructions in order to not overfly runway 17 and avoid the air carrier. Wind 100/9.sequential landing and approaches on intersecting runways by aircraft with differing performance and visibility characteristics (air carrier vs. High wing cessna with limited side-upward see and avoid during low approach) should be considered only if adequate separation can be assured and if traffic density in the primary runway closed VFR pattern is light. That was not the case in this circumstance and the air carrier should have been vectored to runway 8 or we should not have been cleared for low approach to runway 8 until after the air carrier had landed.
Original NASA ASRS Text
Title: C172 Flight Instructor with student is cleared for a low approach only while an air carrier is cleared to land on the intersecting runway. The air carrier elects to go around resulting in an airborne conflict at the runway intersection with the C172 taking evasive action.
Narrative: Primary runway in use was Runway 8. We (C-172 in closed traffic) were cleared for low approach #2 following air carrier on straight in approach/landing on Runway 8. An air carrier had been cleared for landing several miles north of the airport on Runway 17. At least 3 Skyhawks were in close traffic for Runway 8 and 2 air carriers were holding short Runway 17. During our approach to Runway 8 and near/past the threshold the air carrier executed a go around Runway 17 and we executed steep left climbing turn following Tower instructions in order to not overfly Runway 17 and avoid the Air Carrier. Wind 100/9.Sequential landing and approaches on intersecting runways by aircraft with differing performance and visibility characteristics (air carrier vs. high wing Cessna with limited side-upward see and avoid during low approach) should be considered ONLY if adequate separation can be assured and if traffic density in the primary runway closed VFR pattern is light. That was not the case in this circumstance and the air carrier should have been vectored to Runway 8 or we should not have been cleared for low approach to Runway 8 until after the Air Carrier had landed.
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.