XJT AIP
- Thread starter ComplexHiAv8r
- Start date
surreal1221
Well-Known Member
Yeah, not really sure you can use the be that as it may and then qualify it by saying or may not...lol
But hey - we are just simple XJT pilots who like to have a drink every now and then.
But hey - we are just simple XJT pilots who like to have a drink every now and then.
Autothrust Blue
Welcome aboard the Washington State Ferries
I've always seen that expression rendered "be that as it may," but that may, or may not be the correct way.
mastermags
Well-Known Member *giggity*
I'm guessing he's still upset about Saturday night.
Autothrust Blue
Welcome aboard the Washington State Ferries
Forget what?
I've suppressed all memory of saturday night forever and ever.
PhilosopherPilot
Well-Known Member
It is for the ERJ, but not the CRJ.
Edit-- I'm not saying it can't be programmed, or captured as a derived parameter on the CRJ ACARS. I'm just saying it's not a recorded parameter on the FDR.
Last edited:
BobDDuck
Island Bus Driver
But Gps derived ground speed is.
PhilosopherPilot
Well-Known Member
Yeah, but it is horribly unreliable below 50 knots or so. It wouldn't be a good option. The best option would be to connect to the prox system directly with the ACARS and look for wheel movement. I'm not certain if the current ACARS wiring configuration captures that parameter though. It prob would require some rewiring.
BobDDuck
Island Bus Driver
PSA's 200s were triggered by wheel movement. The 700s were triggered by GPS groundspeed > 5 knots. The 200s triggered pretty reliably. The 700s sometimes wouldn't trigger until you started your forward taxi, but at WAY less than 50 knots.
PhilosopherPilot
Well-Known Member
Yeah, I'm just saying the parameter is shaky. It might be good enough for this purpose, but it SUCKED for the level of detail that we wanted for FOQA. It gave us lots of false positives when looking for aircraft taxi events. False positives = a ton of validation work, so we abandoned the parameter, and used derived parameters from a few other sources, like N1 > idle combined with a heading change = aircraft in motion, etc.
It's entirely possible that PSA has a different setup than ASA though. Maybe they had wheel motion in the FDR bus, but I figured that most CL-65 had the same configuration.
(Sorry for the off- topic post.)
It's entirely possible that PSA has a different setup than ASA though. Maybe they had wheel motion in the FDR bus, but I figured that most CL-65 had the same configuration.
(Sorry for the off- topic post.)
Last edited:
jtrain609
Antisocial Monster
You mean you guys LOOKED for guys taxing too fast?
Let me tell you a funny story about negotiations for contract '04 on this side...
The company thought our guys were involved in a work slowdown, so they were hanging out around the airport with binoculars, and if guys weren't taxing around with the speed brakes up (wheel speed over 25 knots and thrust below a certain angle, so basically over 25 knots) they were getting called into the CPO to have a discussion about their "work slowdown."
At 25 knots.
We taxi like Southwest over here.
PhilosopherPilot
Well-Known Member
Nah, we were looking for aircraft configuration changes during taxi. We needed a reliable way to tell when the aircraft started taxi so we could chart the average time that the crews set flaps for takeoff. (We had a few attempted takeoffs with flaps at zero.) FOQA is about aggregate data, not specific people. We actually used the data to drive a checklist change.
jtrain609
Antisocial Monster
Look at our data too? It happens about 2 minutes prior to departure with the old schoolers.
Oh and there's that pesky gust lock...
Autothrust Blue
Welcome aboard the Washington State Ferries
Ewwww.
surreal1221
Well-Known Member
jtrain609 said:
That thing'll kill someone, eventually.