On my last flight in cruise, my HDX display indicated 18 deg of flap was selected with a flap over speed announcement despite zero flap deployed. This lasted for a few seconds and then cleared, but it happened several more times. I slowed the aircraft to flap limiting speed the next time it happened and cycled the flaps which again zeroed the flap position on the screen, but it happened once more during the flight. im thinking this might be a sensor issue. The aircraft is a Vans Rv 12iS, has anybody else had a similar issue
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Flap position sensor issue
- Thread starter Mweaver6
- Start date
jakej
Well-Known Member
Sensor bad is unlikely IF it's the Ray Allen POS-12, unless it has been damaged.
A picture of the sensor install would/could be very helpful.
Is the sensor wired to operate via an EFIS ? which brand ?, or via a bus system like the VP-X ?
A picture of the sensor install would/could be very helpful.
Is the sensor wired to operate via an EFIS ? which brand ?, or via a bus system like the VP-X ?
DBRV10
Active Member
Sensor bad is unlikely IF it's the Ray Allen POS-12, unless it has been damaged.
A picture of the sensor install would/could be very helpful.
Is the sensor wired to operate via an EFIS ? which brand ?, or via a bus system like the VP-X ?
Jake, you say that.........BUT.....just last month, straight out of the box, a completely faulty POS-12. Yep.....even I know thats unlikely and wasted all manner of time checking everything else..........DOA from the box. It was an internal fault in the pot. Mechanical fault of the pot because you could get it to function about 5% of the time and only part of the length of travel.
I never expected it, but now, never say never.
i have tracked the source of the problem to a broken wire from the potentiometer on the flap motor. On an Rv12 the motor and position sensor is all part of the same actuator unit. In this instance it was an intermittent fault and difficult to track, but is now resolved. Thanks to everyones input