 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
SR22 pilot reports notams printed prior to departure are unreadable but did not cause any other problems.
| Attributes | |
| ACN | 827860 |
| Time | |
| Date | 200903 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | OMA.Airport |
| State Reference | NE |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | SR22 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Landing Taxi |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying Single Pilot |
| Qualification | Flight Crew Instrument Flight Crew Private |
| Experience | Flight Crew Last 90 Days 30 Flight Crew Total 675 Flight Crew Type 465 |
| Events | |
| Anomaly | Other NOTAM Readability |
Narrative:
While landing on runway 32L at oma I was being followed by other aircraft. No incursion or safety issues. I was exiting runway 32R to left on taxiway delta; but due to a runway closure reversal runway 32L was closed now runway 32R was closed; I was not well enough informed on usable taxiways. I had studied the notams in detail the day before the flight and knew that runway 32L and taxiway charlie were closed. The morning of the flight again reviewed the notams; printed a copy of weather and notams to review in flight for each flight leg. However; did not catch that runway closure was now switched to runway 32R and not runway 32L. In flight went to review notams; but last leg was printed in hyper graphics and unreadable. Upon landing expected taxi turn off directions from tower; as I was being followed in by other aircraft. Was able to make a nice short landing and take first taxiway to the left which was 'D.' the other plane was about to land as I cleared the runway. I learned the following: 1) I had printed the notams and weather; but the notams were hyper graphic and unreadable. In future will make sure all copies of support documents are readable. 2) especially when construction is involved; be very diligent in verifying notams changes. 3) query tower for expect taxiway exit to use when time may be critical. Plan the landing to match expected taxiway exit to minimize runway taxi time.
Original NASA ASRS Text
Title: SR22 pilot reports NOTAMs printed prior to departure are unreadable but did not cause any other problems.
Narrative: While landing on Runway 32L at OMA I was being followed by other aircraft. No incursion or safety issues. I was exiting Runway 32R to left on Taxiway Delta; but due to a runway closure reversal Runway 32L was closed now Runway 32R was closed; I was not well enough informed on usable taxiways. I had studied the NOTAMs in detail the day before the flight and knew that Runway 32L and Taxiway Charlie were closed. The morning of the flight again reviewed the NOTAMs; printed a copy of weather and NOTAMs to review in flight for each flight leg. However; did not catch that runway closure was now switched to Runway 32R and not Runway 32L. In flight went to review NOTAMs; but last leg was printed in hyper graphics and unreadable. Upon landing expected taxi turn off directions from Tower; as I was being followed in by other aircraft. Was able to make a nice short landing and take first taxiway to the left which was 'D.' The other plane was about to land as I cleared the runway. I learned the following: 1) I had printed the NOTAMs and weather; but the NOTAMs were hyper graphic and unreadable. In future will make sure all copies of support documents are readable. 2) Especially when construction is involved; be very diligent in verifying NOTAMs changes. 3) Query Tower for expect taxiway exit to use when time may be critical. Plan the landing to match expected taxiway exit to minimize runway taxi time.
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.