KAP 140 trouble

On Tue, 26 Jun 2007 19:43:58 -0500, "Dan Luke"
wrote:


"Peter Clark" wrote:

Have they tried
hooking up the pitot/staic testset and pumping it up?

Don't know. They're getting complete schematics from Garmin for further
trouble shooting.

The baseline schematics from Garmin won't neccessarily match how
Cessna has it set up. They should be looking at the wiring diagrams
on the Cessna maintenance manual CD. Have they called Cessna about
this?

"Peter Clark" wrote:

Don't know. They're getting complete schematics from Garmin for further
trouble shooting.

The baseline schematics from Garmin won't neccessarily match how
Cessna has it set up. They should be looking at the wiring diagrams
on the Cessna maintenance manual CD. Have they called Cessna about
this?

That's the same thing John Jones on the CPA forum said.

I'll ask them tomorrow.

--
Dan
T-182T at BFM

The tech called me this afternoon and said the problem is indeed in the KAP
140 computer. How this jibes with the story I got last week that the unit
had been swapped, I don't know.

The new part will be in Tuesday. I'll report then if that truly fixes
things.

--
Dan
T-182T at BFM

"Peter" wrote:

The tech called me this afternoon and said the problem is indeed in the KAP
140 computer. How this jibes with the story I got last week that the unit
had been swapped, I don't know.

Hmmm.... it is far from unknown for things that have been swapped to
not actually having been swapped. I've had this several times.

Yep.

Back in prehistoric times when I was a tech, I did it myself. Only after I
drove 90 miles back to town did I notice the new date code on the controller I
was bringing back.

Could've happened this time.

--
Dan
T-182T at BFM

It was the KAP 140 computer.

Test flew it this morning and it checked out ok.

Seems like the shop could have found this out a lot sooner, seeing as how
they're a Honeywell B/K dealer & authorized warranty shop.


--
Dan
T-182T at BFM

On Thu, 12 Jul 2007 11:11:16 -0500, "Dan Luke"
wrote:


It was the KAP 140 computer.

Test flew it this morning and it checked out ok.

Seems like the shop could have found this out a lot sooner, seeing as how
they're a Honeywell B/K dealer & authorized warranty shop.

Beyond that, two different people identified it as the computer based
on your original recitation of the problem site unseen. I'd find a
new avionics shop.