Narrative:

I inadvertently entered two forest service fire tfrs; ZLA 6/7364 tfr (2006-7364-1)and ZLA 6/9952 tfr(2006-9952-1); along my route of flight that I thought were inactive. When I discovered a contracted air attack fire aircraft in 6/7364; I tried contacting him on our forest service flight following frequency but he had turned it off. Two of our dispatch centers failed to tell either one of us that the other was in the area even though they were tracking us on our aff (automated flight following) system. They eventually told me who I needed to call so they were in contact with us both. I left the area to the north and ran through 6/9952 where there were no aircraft. At no time was there any close encounter with any aircraft. When I contacted the flight operations officer on the ground; he said no fixed-wing aircraft were to be used in either area but they were going to work the ground for another week. The tfrs should have been removed because they both encompassed large areas up to as high as 13;000 MSL. This tying up of airspace has been a complaint by the public and the FAA for years. When I contacted the forest service air attack officer in the air attack aircraft; he confirmed he knew who I was and that they did not intend to use anymore fixed-wing aircraft and only a couple of helicopters. The dispatchers need to contact all the aircraft of potential conflicts immediately. The mistake I made was not knowing they were still active and not trying to contact somebody before I entered the areas. I fully acknowledge my honest mistake (once in years of federal service) but I would like to emphasize that all the players; dispatchers; incident commanders; and pilots need to work as a team; keep track of what is going on; and communicate all potential conflicts. That is everyone's responsibility.

Related reports:

Google
 

Original NASA ASRS Text

Title: Pilot reported he entered two TFR's that were assumed deactivated.

Narrative: I inadvertently entered two Forest Service fire TFRs; ZLA 6/7364 TFR (2006-7364-1)and ZLA 6/9952 TFR(2006-9952-1); along my route of flight that I thought were inactive. When I discovered a contracted Air Attack fire aircraft in 6/7364; I tried contacting him on our Forest Service flight following frequency but he had turned it off. Two of our dispatch centers failed to tell either one of us that the other was in the area even though they were tracking us on our AFF (Automated Flight Following) system. They eventually told me who I needed to call so they were in contact with us both. I left the area to the north and ran through 6/9952 where there were no aircraft. At no time was there any close encounter with any aircraft. When I contacted the flight operations officer on the ground; he said no fixed-wing aircraft were to be used in either area but they were going to work the ground for another week. The TFRs should have been removed because they both encompassed large areas up to as high as 13;000 MSL. This tying up of airspace has been a complaint by the public and the FAA for years. When I contacted the Forest Service Air Attack officer in the Air Attack aircraft; he confirmed he knew who I was and that they did not intend to use anymore fixed-wing aircraft and only a couple of helicopters. The dispatchers need to contact all the aircraft of potential conflicts immediately. The mistake I made was not knowing they were still active and not trying to contact somebody before I entered the areas. I fully acknowledge my honest mistake (once in years of federal service) but I would like to emphasize that all the players; dispatchers; incident commanders; and pilots need to work as a team; keep track of what is going on; and communicate all potential conflicts. That is everyone's responsibility.

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.