37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 833820 |
Time | |
Date | 200905 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | BRD.Airport |
State Reference | MN |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
Operating Under FAR Part | Part 91 |
Flight Phase | Taxi |
Route In Use | Direct |
Flight Plan | None |
Person 1 | |
Function | Pilot Flying |
Qualification | Flight Crew Instrument Flight Crew Flight Instructor Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 30 Flight Crew Total 6150 Flight Crew Type 650 |
Events | |
Anomaly | Deviation - Procedural Clearance Ground Incursion Taxiway |
Narrative:
Flew to a nearby airport; brd. Two runways where closed at the brd airport due to a resurfacing project. We therefore needed to depart on a runway that we seldom used. While taxing to the active runway we inadvertently turned onto a restricted taxiway that led to a department of natural resources fire base. This taxiway angled off of the taxiway we were on at more than a 90 degree angle from our taxi direction and appeared to provide a direct route to the departure end of the active runway. After realizing that we were heading towards the fire base ramp; we turned around and went back to the taxiway we had been on. After turning back onto the taxiway we had been on; we could now see that there was a sign indicating that the other taxiway was restricted but this sign was not visible from the direction that we had been taxing because of the angle of the taxiway. The restricted sign appeared to be temporary (used only during fire season?) and we speculated that a sign that should have been visible from the direction we had been taxing could have fallen down or simply not been put up. We also noted that two sets of taxiway diagrams we had for the airport; commercial IFR charts and the state of minnesota airport directory; did not show that the taxiways or ramp near the fire base were restricted.
Original NASA ASRS Text
Title: PA28 instructor and student inadvertently turn onto a restricted taxiway; stating signage was not visible.
Narrative: Flew to a nearby airport; BRD. Two runways where closed at the BRD airport due to a resurfacing project. We therefore needed to depart on a runway that we seldom used. While taxing to the active runway we inadvertently turned onto a restricted taxiway that led to a Department of Natural Resources fire base. This taxiway angled off of the taxiway we were on at more than a 90 degree angle from our taxi direction and appeared to provide a direct route to the departure end of the active runway. After realizing that we were heading towards the fire base ramp; we turned around and went back to the taxiway we had been on. After turning back onto the taxiway we had been on; we could now see that there was a sign indicating that the other taxiway was restricted but this sign was not visible from the direction that we had been taxing because of the angle of the taxiway. The restricted sign appeared to be temporary (used only during fire season?) and we speculated that a sign that should have been visible from the direction we had been taxing could have fallen down or simply not been put up. We also noted that two sets of taxiway diagrams we had for the airport; commercial IFR charts and the state of Minnesota airport directory; did not show that the taxiways or ramp near the fire base were restricted.
Data retrieved from NASA's ASRS site as of April 2012 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.