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

Did I bust a Reg?

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
Cookmg:

Good thread and something that I think other "new" pilots wonder about.

1.) Like everyone else said file a "NASA" report even if just for the fun of the experience. Remember, there is a reason it's called a NASA report - the personal information is held between you and NASA. NASA is NOT the FAA! Your information will remain confidential unless the act you report is such a serious infraction that you do not qualify for immunity. That said, no one in your future will ever see that you filed this report. To date, I've probably filed something like 20 NASA reports for all kinds of things from stupid mistakes on my part to outright near-air collisions caused by ATC errors. The FAA gets the contents of your report (without your name) and it goes into a great big safety database. Do your fellow pilots a favor and file the report. Oh and I'm with a 121 carrier and just filed a NASA report the other day. Best insurance policy a pilot can have.

2.) On the Class B / Class D thing, it needs a NASA report because it is something that ATC does to us pilots all the time. They have "turf wars" over airspace and we lose. Philly Class B and Wilmington Class D is a good example. Philly will often drop you on ILG's doorstep and just say contact tower. You merrily fly on into Class D thinking they've affected a handoff and get chewed out by tower who doesn't know a thing about you. Pilots get lulled into a sense of ease on this stuff because the ATC guys "normally" take care of us. But when they are having a bad day, WE can become the fall guys.

3.) On the fear of future implications, I think you fear too much. This is not the interview breaker - this is just good experience and I think you should pat yourself on the back for having recognized the potential problem and being very astute about airspace regulations. I'm not wishing anything bad on you, but most us have far larger skeletons in our closet and still manage to survive the interview process. A lot of folks think they need to go to an interview with a squeaky clean resume and background. Got to tell you, if the airlines only hired folks with perfect records, there'd only be about 18 pilots in the hiring pool. People bend metal, do young and stupid things that teenagers and college kids do, they break regs, they fail checkrides and yet they still seem to get hired. A good pilot is always learning. Judgement comes from experience. Experience comes from surviving bad judgement. Go figure.
 
Most controllers are not out to bust every pilot that has incurred a minor infraction. The ones that get busted are the ones that blatantly bust a reg. eg: flying through a particular airspace without attempting to contact anyone. You made an effort to do it properly. I don't think anyone would make sure you were busted for that.
 
My two cents:

What you are looking at here is the difference between the standards used to define "communication" for class D and class C airspace.

As soon as the class D controller communicated with you, and did NOT tell you to remain clear of the class D airspace, you were covered. The key is to make that call to the Delta controller before you enter his airspace.

Most of what was discussed above applies to the more stringent requirements of class C airspace. There, the controller must address you by your tail number or callsign for your entry, or may say "aircraft calling Allentown stand by", or "N32B remain clear of the class Charley" in which case you may NOT enter.

Case in point: not long ago, I had to fly VFR into Caldwell, and I used radar advisories from Allentown and New York approach. The New York controller waited until I was almost ready to turn downwind for landing befrore he cut me loose to Caldwell tower. After a phone call (not at the tower's request, we volunteered) we discovered that this is something that NY does very frequently, much to Caldwell's chagrin.

Lesson learned: use the other pilot, and the second radio, to alert the class D controller to what is happening, and that the controller for the overlying airspace is working you for traffic separation. (Important note: he was not "providing separation" he was advising me and the other traffic so WE could "provide separation")

No violation for you, cookmg. :)
 
Last edited:
I say don't sweat it if the controllers didn't say anything to indicate otherwise... Once a particular action is questioned by a controller though... yeah... you might want to file the ol' NASA report just in case. IMHO.
 
NASA form

Are you an AOPA member? If so, you can either print a NASA form from their website or call the 800 number and they will fax you one. They are very helpful.

Good Luck
 
File a NASA report to CYA, but don't worry about it. The controller probally didn't even notice, most class Delta's don't legaly have radar, all they have is a D Bright display, which is (according to my controller friend), not legally allowed to be used except for SA.

My friend also tells that, controllers hate to write you up its more paperwork for them. Most calls are scoldings unless you did something seriously wrong, and on purpose.
 

Latest resources

Back
Top