70
edits
John Denker (talk | contribs) (Navigation database out-of-date) |
John Denker (talk | contribs) (Wild accelerations at low speed) |
||
| Line 116: | Line 116: | ||
any airport and tune up the localizer (since relatively few | any airport and tune up the localizer (since relatively few | ||
localizers have DME). | localizers have DME). | ||
==== Wild accelerations at low speeds ==== | |||
Improper inclinometer ball indications have been observed: | |||
-- When parked, the ball was pegged to one side. | |||
-- When taxiing at low speeds (a few knots or less) the ball | |||
oscillated wildly back and forth. | |||
This was observed in the c182 model and in the default c172 model. | |||
Tracing indicates that the problem is not within the slip_skid_ball.cxx | |||
code, but rather upstream of there, in the flight dynamics. Tracing | |||
shows that the y-accel-fps_sec values are wildly fluctuating in | |||
direction, and enormous in magnitude. | |||
Additional evidence pointing to the FDM comes from the fact that | |||
the problem is observed with JSBSim and not with larcsim (although | |||
larcsim has other problems, such as drifting slowly sideways while | |||
parked). | |||
This is important from a procedures training point of view. | |||
If you want to have | |||
a realistic flight, one of the checklist items is to verify, insofar | |||
as possible, that the instruments give correct indications during | |||
preflight and taxi. In a real aircraft, a pilot who found the | |||
inclinometer pegged would cancel the flight before even starting | |||
the engine. | |||
==== Airport lighting in poor weather ==== | ==== Airport lighting in poor weather ==== | ||
edits