37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1541008 |
Time | |
Date | 201805 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Transport Low Wing 2 Recip Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | None |
Flight Plan | None |
Person 1 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Engineer Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor |
Experience | Flight Crew Last 90 Days 62 Flight Crew Total 19000 Flight Crew Type 43 |
Events | |
Anomaly | Airspace Violation All Types Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
Narrative:
I was flying copilot on a vintage transport aircraft in passenger configuration. Boarding and deplaning were on the ramp; and the flight was to go over the standard ride route; which we both knew well. The preflight briefing had been self-accomplished in the morning using the seattle avionics' qefb program; but unfortunately; the 'tfr' layer was not turned on as it usually is. The weather was beautiful and forecast to remain that way all day; but hot - almost 100 degrees; and so the aircraft interior on the ground would be uncomfortably hot for the passengers until we got airborne and had some air flow through the cabin. This was especially important on the first flight of the day as a full run up is required on the first flight; which takes a few minutes longer than later flights. Getting the airplane pre-flight; turned around and positioned on the ramp; our two flight attendants briefed; as well as coordinating arrival / departure procedures with the ramp crew took more time than we thought; and the first set of (enthusiastic) passengers were ready to board on time. Getting in the cockpit and starting the checklist; I elected not to take time to strap my ipad with seattle avionics' qefb on to my leg. The plane had just had the avionics upgraded with; among other things; a traffic display on the garmin gtn 750 & 650; the weather was perfect; I knew the route; it was hot... So I just didn't take time to strap on and use the ipad; as it didn't seem necessary. During the flight; as we were passing ZZZ airport; which is non-controlled; I made a courtesy position report on CTAF even though we weren't landing; and the reply we received informed us that we were flying in their tfr during an air show. We departed the area via the shortest direction possible; and upon landing at departure airport [we] were instructed to call a certain phone number for a possible pilot deviation; and the captain made the call while I listened. The new avionics showed the traffic; but I hadn't thought that it wouldn't show tfrs; as does the qefb program on my ipad - if it is selected. We used the ipad on the next flights.
Original NASA ASRS Text
Title: First Officer reported a TFR violation occurred because he failed to use his iPad's electronic flight bag to identify airspace restrictions.
Narrative: I was flying copilot on a Vintage Transport Aircraft in passenger configuration. Boarding and deplaning were on the ramp; and the flight was to go over the standard ride route; which we both knew well. The preflight briefing had been self-accomplished in the morning using the Seattle Avionics' QEFB program; but unfortunately; the 'TFR' layer was not turned on as it usually is. The weather was beautiful and forecast to remain that way all day; but hot - almost 100 degrees; and so the aircraft interior on the ground would be uncomfortably hot for the passengers until we got airborne and had some air flow through the cabin. This was especially important on the first flight of the day as a full run up is required on the first flight; which takes a few minutes longer than later flights. Getting the airplane pre-flight; turned around and positioned on the ramp; our two Flight Attendants briefed; as well as coordinating arrival / departure procedures with the ramp crew took more time than we thought; and the first set of (enthusiastic) passengers were ready to board on time. Getting in the cockpit and starting the checklist; I elected not to take time to strap my iPad with Seattle Avionics' QEFB on to my leg. The plane had just had the avionics upgraded with; among other things; a traffic display on the Garmin GTN 750 & 650; the weather was perfect; I knew the route; it was hot... so I just didn't take time to strap on and use the iPad; as it didn't seem necessary. During the flight; as we were passing ZZZ airport; which is non-controlled; I made a courtesy position report on CTAF even though we weren't landing; and the reply we received informed us that we were flying in their TFR during an air show. We departed the area via the shortest direction possible; and upon landing at Departure airport [we] were instructed to call a certain phone number for a possible pilot deviation; and the Captain made the call while I listened. The new avionics showed the traffic; but I hadn't thought that it wouldn't show TFRs; as does the QEFB program on my iPad - if it is selected. We used the iPad on the next flights.
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.