37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1322692 |
Time | |
Date | 201601 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ABE.Airport |
State Reference | PA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | M-20 Series Undifferentiated or Other Model |
Operating Under FAR Part | Part 91 |
Flight Phase | Landing |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Beechcraft King Air Undifferentiated or Other Model |
Flight Phase | Landing |
Person 1 | |
Function | Single Pilot Pilot Flying |
Qualification | Flight Crew Private Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 3 Flight Crew Total 860 Flight Crew Type 600 |
Events | |
Anomaly | ATC Issue All Types Conflict Ground Conflict Critical Inflight Event / Encounter Weather / Turbulence |
Miss Distance | Horizontal 500 |
Narrative:
I was on a training mission to complete a flight review and ipc on this gusty windy day. Winds were 340/11g21. We were completing the last instrument approach as part of the ipc and finishing up for the day; planning to land full stop out of the ILS 6 at abe. The distance from the runway end to the intersection with runway 31 is not much more (possibly less than) 2;000 feet. During the approach we were given no land and hold short (lahso) instruction; and had one been given I would have declined it as landing out of an ILS to minimums can require significant runway; very often requiring crossing runway 31. The landing was challenging due to the gusty winds; and after landing and during rollout I was given a 'hold short of runway 31 - landing traffic' instruction approximately 500 feet from runway 31. As I looked to my right there was a king air that rotated and was about to touch down on 31; and had we not been able to stop (or had to execute a late go-around); there could have been a serious incident. The controller clearly put himself in a bad situation and did not take steps to correct it in a timely manner.fortunately the strong gusty winds that day allowed for a very short rollout in the mooney and we were able to stop and make a turn prior to runway 31; which is usually not the case when flying that approach.
Original NASA ASRS Text
Title: Mooney pilot reported a ground conflict after landing at ABE. Reporter stated this could have developed into a dangerous situation.
Narrative: I was on a training mission to complete a flight review and IPC on this gusty windy day. Winds were 340/11G21. We were completing the last instrument approach as part of the IPC and finishing up for the day; planning to land full stop out of the ILS 6 at ABE. The distance from the runway end to the intersection with Runway 31 is not much more (possibly less than) 2;000 feet. During the approach we were given no Land and Hold Short (LAHSO) instruction; and had one been given I would have declined it as landing out of an ILS to minimums can require significant runway; very often requiring crossing Runway 31. The landing was challenging due to the gusty winds; and after landing and during rollout I was given a 'Hold Short of Runway 31 - landing traffic' instruction approximately 500 feet from Runway 31. As I looked to my right there was a King Air that rotated and was about to touch down on 31; and had we not been able to stop (or had to execute a late go-around); there could have been a serious incident. The controller clearly put himself in a bad situation and did not take steps to correct it in a timely manner.Fortunately the strong gusty winds that day allowed for a very short rollout in the Mooney and we were able to stop and make a turn prior to Runway 31; which is usually not the case when flying that approach.
Data retrieved from NASA's ASRS site 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.