37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1372570 |
Time | |
Date | 201507 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | JVW.Airport |
State Reference | MS |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | Landing |
Route In Use | Visual Approach |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Commander 114/A/B/TC |
Operating Under FAR Part | Part 91 |
Flight Phase | Landing |
Person 1 | |
Function | Pilot Not Flying Instructor |
Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Commercial Flight Crew Flight Instructor |
Experience | Flight Crew Last 90 Days 350 Flight Crew Total 1000 Flight Crew Type 700 |
Events | |
Anomaly | Conflict Ground Conflict Critical Deviation - Procedural Published Material / Policy Ground Incursion Runway |
Narrative:
The winds were variable; favoring either runway; with clear skies and unrestricted visibility. My student and I were doing touch and goes on runway 12 for approximately 1 hour and making position announcements. As my student and I had touched down on runway 12; I realized an aircraft was crossing the localizer and proceeding to land on the same runway in the opposite direction (runway 30). Aircraft was not making position announcements. We slammed on the brakes to turn on taxiway foxtrot; because if we did not; we would have ended up in the same place at the same time head on. As my student and I exited the runway and ran checklists; I informed unicom of the runway incursion. Aircraft made his first announcement saying the winds were favorable for either runway.
Original NASA ASRS Text
Title: C172 instructor pilot reported braking abruptly and taking a taxiway turnoff to avoid a ground conflict with an aircraft landing opposite direction at JVW without any announcements on CTAF.
Narrative: The winds were variable; favoring either runway; with clear skies and unrestricted visibility. My student and I were doing touch and goes on runway 12 for approximately 1 hour and making position announcements. As my student and I had touched down on runway 12; I realized an aircraft was crossing the localizer and proceeding to land on the same runway in the opposite direction (runway 30). Aircraft was not making position announcements. We slammed on the brakes to turn on taxiway Foxtrot; because if we did not; we would have ended up in the same place at the same time head on. As my student and I exited the runway and ran checklists; I informed Unicom of the runway incursion. Aircraft made his first announcement saying the winds were favorable for either runway.
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.