Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

Should I fill out a NASA form?

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web
I'm not familar with the gear system in the Arrow, but in general it is not always a good idea to become Joe Test pilot if you suspect a gear problem.

As far as the NASA form goes, heck they don't even need a stamp! Like the other fellow said, don't confess to a crime on the title strip, just put something like "altitude question" or some such.

If you ask yourself if you ought to file one, then you ought to file one. I file one anytime anytime I experience the slightest issue with ATC.
 
JimNtexas said:
I'm not familar with the gear system in the Arrow, but in general it is not always a good idea to become Joe Test pilot if you suspect a gear problem.

As far as the NASA form goes, heck they don't even need a stamp! Like the other fellow said, don't confess to a crime on the title strip, just put something like "altitude question" or some such.

If you ask yourself if you ought to file one, then you ought to file one.

EXACTLY what he said. Word-for-word.
 
I wouldn't give the feds more paperwork with my name on it. If ATC let it go, let it go. Had ATC told you to call them, then by all means, cover your ass. No need to fix it if it isn't broken.
 
I think its anything +/- 200 is a violation. And I have heard that like if you screw up or something the controller will give you a number to call after you land and you can call them or whatever and explain the situation and plead your case or whatever. So you know what he knew at that time and they knew what you knew or whatever was going on, then you might be able to work it out. Its alot better than trying to talk about it on the radio, when you are busy and so are they and you are just holding up a freq. And its better than just a strict report for any wrong doing. But I don't think its that big of a deal, and I dont think I want to waste one of my NASA forms when I might actually need one down the road, you never know what is going to happen I guess. I still can't belive I lost 500 feet in a Arrow without even realizing it, its a big wake up call. I didn't even know anything about them till a few months ago and I was like oh thats neat, I have just never done anything like this before, so its a new experience for me. And I dont want to do anything that has a chance of screwing me getting airline job down the road. Anyway, I think I am just going to let it go, at the time I was just so pissed I let it happen, but now looking back I don't even really thing its an issue. They had my cell number on the flight plan form, but not my address, I figure if they wanted to make an issue about it they would have called or said something then. Thanks for the help guys and gals.
 
Last edited:
FlyJordan said:
I release the pressure in the system and the gear falls and I get 3 green lights. Pull it back up
\


Here is a rule I have for myself (I am not saying you did a thing wrong, and I try never to judge another) and it has worked well:
If I am having a gear problem, and at any point I get three green, I Leave It The Fukk Alone. Maybe gear lights flickering and gear motor cutting in and out is 'normal' for this model? I have no idea but it sounds kinda spooky to me.

Someone on FI.com once said if you notice an altitude deviation, flash the little fingers to the transponder off knob, get back where you belong quickly and then recycle when queried. I can't imagine doing this for more than a few seconds because of the possible loss in safety.
 
FlyJordan said:
I figure if they wanted to make an issue about it they would have called or said something then. Thanks for the help guys and gals.

Sleep tight, tomorrow is another day. Do not worry about it. If they wanted to make an issue out of it, they would have already done so...

My question still remains... what is an altitude violation? 200'. 300'. where can I find this information?
 
GravityHater said:
\


If I am having a gear problem, and at any point I get three green, I Leave It The Fukk Alone. Maybe gear lights flickering and gear motor cutting in and out is 'normal' for this model? I have no idea but it sounds kinda spooky to me.

The reason I was not worried about pulling the gear back up was because I could always do the same thing again. The gear will free fall, so it was all good.
 
Fly_Chick said:
My question still remains... what is an altitude violation? 200'. 300'. where can I find this information?


When you find it please let me know, but I dont know where too.
 
Not a regulation indicating the violation level but it might indicate they are not looking for us unless we exceed 299' deviation from assigned altitudes:

http://www.faa.gov/ATPubs/ATC/Chp5/atc0502.html#5-2-17

5-2-17. VALIDATION OF MODE C READOUT

Ensure that Mode C altitude readouts are valid after accepting an interfacility handoff, initial track start, track start from coast/suspend tabular list, missing, or unreasonable Mode C readouts. For TPX-42 and equivalent systems ensure that altitude readout is valid immediately after identification. (TCDD-/BANS-equipped tower cabs are not required to validate Mode C readouts after receiving interfacility handoffs from TRACONs according to the procedures in para 5-4-3, Methods, subpara a4.)

a. Consider an altitude readout valid when:

1. It varies less than 300 feet from the pilot reported altitude, or

PHRASEOLOGY-
(If aircraft is known to be operating below the lowest useable flight level),

SAY ALTITUDE.

or

(If aircraft is known to be operating at or above the lowest useable flight level),

SAY FLIGHT LEVEL.

2. You receive a continuous readout from an aircraft on the airport and the readout varies by less than 300 feet from the field elevation, or

NOTE-
A continuous readout exists only when the altitude filter limits are set to include the field elevation.
 
File, with generic description of incident on ID Strip.
I have read that 400' deviation triggers bells and whistles at Center. But doesn't matter whether ATC said anything or not. If more than 10 days go by, you haven't filed, and you receive an LOI, you'll wish you had filed. The last FAA enforcement action I worked was an altitude deviation case with a NASA form.
 
If you ever have the slightest question that you may need to file then do so by all means.
 
lawfly said:
File, with generic description of incident on ID Strip.
I have read that 400' deviation triggers bells and whistles at Center. But doesn't matter whether ATC said anything or not. If more than 10 days go by, you haven't filed, and you receive an LOI, you'll wish you had filed. The last FAA enforcement action I worked was an altitude deviation case with a NASA form.

Did it help the pilot?
 
Here is an idea, could I just call center and see if what the deal is?
 
Not to pick on you, fly jordan, just trying to put it in perspective.

This question comes up fairly frequently on this and other forums. It shouldn't. It shouldn't be one of those things you have to ask about. If there's any question, file one. There's no down side to filing. There is no limit, file as many as you want. Except in the case of an intentional violatin or an accident, the FAA should never see your name, NASA removes all identifying information from the report before forwarding the data to the FAA. Of course it is certainly possble for a corrupt FAA official to have a corrupt buddy in NASA who is feeding him info under the table, but the FAA doesn't have a systematic program in place to monitor how many reports someone files.

If something unsafe happens, file a report

If something happens which has any possibility for resulting in a violation against you, file a report.
 

Latest resources

Back
Top Bottom