16 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHINVSHP In case anyone was wondering...
Leading reported evidence
Install tomorrow, probably by me since i want
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed
I am hopping on a plane, console will be installed tomorrow, probably by me since I want to photograph it to share as an article here.
Leading evidence: 'Install tomorrow, probably by me since i want' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Install tomorrow, probably by me since i want' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
Keep and eye out for a Porsche car hauler somwhere between Baltimore and KC, I should go plot a driving route using Mapquest or something and see how long that is supposed to take if driven straight through.
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
Keep and eye out for a Porsche car hauler somwhere between Baltimore and KC, I should go plot a driving route using Mapquest or something and see how long that is supposed to take if driven straight through.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
16 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Planet-9: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T200546Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Is the status my car changed to some time over the weekend. That means the car has been loaded on a car transport and shipped to the dealership. Considering my dealership is as far away from any ocean port as you can get, it could be awhile until it arrives. Somehow I don't picture a truck driver driving all day and night to get the car transport here before I leave town this week. So maybe when I get back into town I'll have something waiting for me. One odd thing is that I checked my dealer's online inventory at their website and my car doesn't show up (although it should because it is now considered in dealer inventory when it reaches INVSHP status) but several other cars that my dealer doesn't have and which my dealer claims aren't even ones they've ordered are showing up in their inventory. Weird....
Keep and eye out for a Porsche car hauler somwhere between Baltimore and KC, I should go plot a driving route using Mapquest or something and see how long that is supposed to take if driven straight through. Here we go:
<div class="time">
Total Est. Time:
<span> 17 hours, 6 minutes[/quote]
</div>
<div class="dist">
Total Est. Distance:
<span>1086.71 miles[/quote]
<span>
[/quote]
</div>
It has been taking two to three weeks to get from San Diego to NM with cars. They make several stops along the way and must not ever achieve the speed limit. I am betting that the next snow storm in NM is the day my Cayman is ready for delivery...
I spoke w/ PASHA yesterday. The car is sitting in the port since the 20th, unloaded from the boat the 21st. Stan told me the Porsche rep was sitting in front of him when I called. I asked him to get the car on a transporter, he laughed and said he would see what he could do. My dealer has not been real helpful or just dosen't get the info. I was told 5-7 days from the port to the dealer.
Patch
That's hard to say exactly, but ship arrived Jan 13th, car finished PDI on Tuesday the 17th, and at some point after Tuesday the 17th it was loaded onto a car carrier. The computer status changed over the weekend so if it truly wasn't loaded until over the weekend then it was in port just overa week for PDI, etc. that includes the MLK holiday when the port was shut down for a day. It could have been loaded up onto a truck almost immediately and the computer not updated until the weekend, so again a little hard to say exactly, but at the very least it is on a car transport truck now...somewhere...out there...
patch2,
Do you have a contact at the trucking company where I can get a status on the truck's position? Geez you'd think I'd have a satellite tracking system for the trucks I could tap into and locate it! Anyone know what trucking line hauls them out of Baltimore? (I'm assuming various ones but maybe it is just one?)
Ken, if its a 17 hour drive then it will take the truck a day and a half to get there.. Truck drivers work 10-12 hour days and some even work as much as 15 hours a day. But Im assuming that the truck has to make frequent stops at other porschedealers to drop the other caymans off. So all in all it should take about 4 days total. I dont see why it should take any longer.
10 hours driving max per DOT , 5 hours work time with 8 hour off duty status after the 15. about 550 miles per shift is average. 2 day run lets just hope your dealer is getting the whole truck of Cars and doesnt stop.