|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||0601 To 1200|
|Locale Reference||airport : ewr|
|Altitude||agl bound lower : 0|
agl bound upper : 0
|Operator||common carrier : air carrier|
|Make Model Name||Medium Large Transport, Low Wing, 2 Turbojet Eng|
|Flight Phase||ground : preflight|
|Affiliation||company : air carrier|
|Function||flight crew : captain|
oversight : pic
|Qualification||pilot : atp|
|Experience||flight time last 90 days : 100|
flight time total : 6000
flight time type : 800
|Function||observation : air carrier inspector|
|Qualification||pilot : atp|
|Anomaly||other anomaly other|
|Independent Detector||other other : unspecified|
|Resolutory Action||none taken : anomaly accepted|
|Consequence||faa : assigned or threatened penalties|
|Air Traffic Incident||other|
FAA inspector from teterboro ramp checks aircraft. Crew not there. The man did not even know what an APU was, which was running. He told every employee he wanted to speak to the captain since 'we left an engine running,' (which was the APU). I had to explain what it was, why it was there, why it can be left running in case of fire, etc, etc. Inspector wanted to violate crew for this, no logbook entry for flight times (non required since aircraft had ACARS), and for not making a logbook entry stating no problems with aircraft (not required to do so). Because of his incompetence, lack of knowledge about air carrier operations, etc, etc, I have to fly all day with the back of my mind wondering how someone like this can put this crew through the FAA hassle and bureaucracy of an enforcement action. People like this (who incidently appeared to hold a grudge against company) should not be allowed to ramp check crews and cause flight crew even more aggravation in an aviation industry that already creates a lot of needless stress.
Original NASA ASRS Text
Title: FLT CREW STATES ACI THREATENED TO TAKE ACTION AGAINST FLT CREW FOR LEAVING AN ACFT PARKED AT THE GATE WITH AN APU RUNNING, PLUS FLT CREW FAILURE TO LOG ACFT FLT TIME THAT IS LOGGED AUTOMATICALLY BY ACARS.
Narrative: FAA INSPECTOR FROM TETERBORO RAMP CHKS ACFT. CREW NOT THERE. THE MAN DID NOT EVEN KNOW WHAT AN APU WAS, WHICH WAS RUNNING. HE TOLD EVERY EMPLOYEE HE WANTED TO SPEAK TO THE CAPT SINCE 'WE LEFT AN ENG RUNNING,' (WHICH WAS THE APU). I HAD TO EXPLAIN WHAT IT WAS, WHY IT WAS THERE, WHY IT CAN BE LEFT RUNNING IN CASE OF FIRE, ETC, ETC. INSPECTOR WANTED TO VIOLATE CREW FOR THIS, NO LOGBOOK ENTRY FOR FLT TIMES (NON REQUIRED SINCE ACFT HAD ACARS), AND FOR NOT MAKING A LOGBOOK ENTRY STATING NO PROBS WITH ACFT (NOT REQUIRED TO DO SO). BECAUSE OF HIS INCOMPETENCE, LACK OF KNOWLEDGE ABOUT ACR OPS, ETC, ETC, I HAVE TO FLY ALL DAY WITH THE BACK OF MY MIND WONDERING HOW SOMEONE LIKE THIS CAN PUT THIS CREW THROUGH THE FAA HASSLE AND BUREAUCRACY OF AN ENFORCEMENT ACTION. PEOPLE LIKE THIS (WHO INCIDENTLY APPEARED TO HOLD A GRUDGE AGAINST COMPANY) SHOULD NOT BE ALLOWED TO RAMP CHK CREWS AND CAUSE FLT CREW EVEN MORE AGGRAVATION IN AN AVIATION INDUSTRY THAT ALREADY CREATES A LOT OF NEEDLESS STRESS.
Data retrieved from NASA's ASRS site as of August 2007 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.