• FreeAdvice has a new Terms of Service and Privacy Policy, effective May 25, 2018.
    By continuing to use this site, you are consenting to our Terms of Service and use of cookies.

Almost run over by airplane

Accident - Bankruptcy - Criminal Law / DUI - Business - Consumer - Employment - Family - Immigration - Real Estate - Tax - Traffic - Wills   Please click a topic or scroll down for more.

stannan

Junior Member
What is the name of your state? Virginia

Not sure if this is the right place to ask this question.

I was working on a runway in a major metropolitan airport here in Va. It was at night and the runway was closed with all lights turned off. All FAA protocols and procedures were followed to ensure runway closure.

My crew and I were driving up the runway to head out for break and noticed an aircraft coming towards the runway. When it did not turn onto one of the taxiways and started heading towards us I got concerned and moved back down the runway to make sure the aircraft was coming to the runway or to park in an adjacent parking area close to the runway. When the aircraft turned to to enter the runway my vehicle headlights and safety light were lighting up the ****pit area. I then heard for the first time over the radio the pilot ask for permission to take off from that runway. The air traffic controller gave permission and I immediately called over the radio stating that my crew and I were on the runway. The plane stopped and the controller called back asking if I was able to move. I said yes and moved to the side and rear o the plane. Protocols state that the aircraft should have then been told to abort the take off and return to an open runway. Instead the plane got permission to continue and powered its engine to full and took off. When the engines powered to full I immediately hit the gas taking my vehicle to the very edge of the runway next to the grass hoping to avoid being killed by the back-blast. One crew member was so shaken by the incident he now works daytime again. Another is still a bit jumpy even when aircraft are far away. I myself had nightmares for that entire week and am still a bit concerned when I notice lights coming close to the runway. I still work on the runway since the job needs to be done and I, while more wary now, still have some faith that at least I will still be vigilant even if the pilots and controllers might not be. The controller did call me back after the aircraft took off to see if we were alright and said he made a mistake and we were not in trouble and it wasn't our fault and not to worry.

I did answer some questions about the incident for the FAA who are supposed to be investigating. My boss said he would look in to it also but as of yet he hasn't an nothing has been done.

So basically my question is do I have any recourse at all or do I need to wait for my employer to look into it himself. We are not employed directly by the airport but are a subcontractor.
 


stannan

Junior Member
Forgot to mention.. other than the nightmares and such, there was no actual physical harm to me or my crew. Again if this is the wrong place to start this discussion sorry. Perhaps a moderator can move it to the proper area if need be.
 

HomeGuru

Senior Member
What is the name of your state? Virginia

Not sure if this is the right place to ask this question.

I was working on a runway in a major metropolitan airport here in Va. It was at night and the runway was closed with all lights turned off. All FAA protocols and procedures were followed to ensure runway closure.

My crew and I were driving up the runway to head out for break and noticed an aircraft coming towards the runway. When it did not turn onto one of the taxiways and started heading towards us I got concerned and moved back down the runway to make sure the aircraft was coming to the runway or to park in an adjacent parking area close to the runway. When the aircraft turned to to enter the runway my vehicle headlights and safety light were lighting up the ****pit area. I then heard for the first time over the radio the pilot ask for permission to take off from that runway. The air traffic controller gave permission and I immediately called over the radio stating that my crew and I were on the runway. The plane stopped and the controller called back asking if I was able to move. I said yes and moved to the side and rear o the plane. Protocols state that the aircraft should have then been told to abort the take off and return to an open runway. Instead the plane got permission to continue and powered its engine to full and took off. When the engines powered to full I immediately hit the gas taking my vehicle to the very edge of the runway next to the grass hoping to avoid being killed by the back-blast. One crew member was so shaken by the incident he now works daytime again. Another is still a bit jumpy even when aircraft are far away. I myself had nightmares for that entire week and am still a bit concerned when I notice lights coming close to the runway. I still work on the runway since the job needs to be done and I, while more wary now, still have some faith that at least I will still be vigilant even if the pilots and controllers might not be. The controller did call me back after the aircraft took off to see if we were alright and said he made a mistake and we were not in trouble and it wasn't our fault and not to worry.

I did answer some questions about the incident for the FAA who are supposed to be investigating. My boss said he would look in to it also but as of yet he hasn't an nothing has been done.

So basically my question is do I have any recourse at all or do I need to wait for my employer to look into it himself. We are not employed directly by the airport but are a subcontractor.
**A: you have no claim.
 

HomeGuru

Senior Member
Forgot to mention.. other than the nightmares and such, there was no actual physical harm to me or my crew. Again if this is the wrong place to start this discussion sorry. Perhaps a moderator can move it to the proper area if need be.
**A: your employer could assist with counseling for you and your coworkers.
 

stannan

Junior Member
Thanks for the replies.

Wasn't sure. Did find out that the FAA is charging both pilot and controller. Looks like I have to go and answer more questions for them and possibly testify I was told. I believe the charge the FAA is looking at is some kind of endangerment. The pilot and controller both are in danger of being fired. Just knowing now that they are going to be held responsible makes me feel so much better.

Thanks again for everyone's replies.
 

HomeGuru

Senior Member
Thanks for the replies.

Wasn't sure. Did find out that the FAA is charging both pilot and controller. Looks like I have to go and answer more questions for them and possibly testify I was told. I believe the charge the FAA is looking at is some kind of endangerment. The pilot and controller both are in danger of being fired. Just knowing now that they are going to be held responsible makes me feel so much better.

Thanks again for everyone's replies.
**A: keep us posted.
 

stannan

Junior Member
Update:
The FAA is no longer handling the investigationn. It has been turned over to the NTSB. Not sure what exactly that means if anything for the potential outcome.
 

stannan

Junior Member
So the NTSB is above the FAA? I didn't know that, thought it was the other way around. Thanks learned something new.
 
Last edited:

lya

Senior Member
I just want to thank the OP for an attention-grabbing headline and a most interesting story!

Thank you!
 

stannan

Junior Member
Update 2:

Well it has happened again. Last night to be exact but instead of palne taking off it was landing and turning into a high sped turnoff. This time it was a smaller prop plane, not a jet and almost disaterous consequenses. The plane swerved to the side and one crew member ran and dove to the other side and I jumped in vehicle and slammed on gas peddle driving into the grass area with doors open almost falling out. Another investigation is now pending. Needless to say I will not be working on runways and taxiways for a while. Boss is furious and put job on hold.
 

stannan

Junior Member
additional updates:

Investigation is still ongoing and is now a combined effort between both the FAA and the NTSB along with whoever is in charge of the Air Traffic Controllers. It turns out the second incident involved not only the same controller but the same company that owned the first aircraft.

Any thoughts? Just curious.
 

Ozark_Sophist

Senior Member
additional updates:

Investigation is still ongoing and is now a combined effort between both the FAA and the NTSB along with whoever is in charge of the Air Traffic Controllers. It turns out the second incident involved not only the same controller but the same company that owned the first aircraft.

Any thoughts? Just curious.
This is happening at Washington Dulles International Airport? Aircraft operated by National Jets, Inc?

So much for security. And I know who not to charter with--ha, like I could.

http://www.ntsb.gov/ntsb/brief.asp?ev_id=20070927X01453&key=1
 

Find the Right Lawyer for Your Legal Issue!

Fast, Free, and Confidential
data-ad-format="auto">
Top