Beat your speeding ticket with an Expert Witness

In Ontario, speeding tickets are very hard to beat because the caselaw basically allows the Justice of the Peace and the Judge to simply accept what the officer says as fact. If the officer says you were speeding, then it must be true! If the officer says they were trained on the Radar or Lidar device, then it must be true! If the officer says the device was working properly at the time, then it must be true! Of course we know that just because the officer believes the Radar or Lidar was working properly, does not mean it actually was. With an expert witness, you can then challenge the credibility of the officers statements and bring evidence that shows the device may not have been accurate at the time it was used.

You should also read the following post on why you need an Expert Witness: Caselaw regarding the need for an Expert Witness

Caselaw regarding the need for an Expert Witness for Speeding Trials

This is not legal advice and is for informational purposes only.

The purpose of an expert witness is to bring unbiased information to the court so the Justice of the Peace or Judge can make a better informed decision. An expert witness possesses special knowledge and experience going beyond that of the trier of fact. (see R. v. Beland, [1987] 2 S.C.R. 398, at paragraph 16).

In Ontario, the courts simply take at face value the officers statement that they are a qualified radar/lidar operator and that they believe the device was working properly at the time, and therefore the speed reading was correct. Even cross-examination of the officer on these points is mostly useless because the court will say “there is no statuatory requirement as to what a qualified operator is, so they say they were trained, so it must be true, and they say it was working properly, so it must be true”.

The only way to you can beat it, is for the defence to put their own expert on the stand who can explain why the device has a very good chance of NOT being accurate (since they are NEVER calibrated in Ontario).
Continue reading

What to do when pulled over by police in Ontario or Canada

This is not legal advice and is for informational purposes only.

When you are detained by police (pulled over at the side of the road, DUI/RIDE checkpoint, etc), section 10(a) of the Canadian Charter of Rights and Freedoms requires them to tell you why. So whenever you are stopped, and they come to your vehicle window, immediately ask them:

* Why did you stop me?
* Am I being detained?

Be nice and be polite (they have guns), but remember you do not have to answer any questions. Always answer “I CHOOSE NOT TO ANSWER ANY QUESTIONS, THANK YOU” or “I DO NOT WISH TO MAKE A STATEMENT, THANK YOU” to everything they ask you. This is your fundamental right to be free from self-incrimination and therefore not provide police with evidence that may be used against you. Everything you say can and will be used against you in a court of law. Also remember that you should never lie to police. It much better to say “no comment” than to lie.
Continue reading

R vs Jordan- Right to a Speedy Trial- Charter Section 11b Argument

This is not legal advice and is for informational purposes only.

In Ontario, your right to a speedy trial used to kick in after 10 to 12 months, but with the Jordan decision, it was (sort of) raised to 18 months.

The following are my thoughts and comments on the R v Jordan 2016 SCC 27, [2016] 1 SCR 631 decision regarding the Right to a Speedy Trial under Charter Section 11b.

You can find it here if you want to read it yourself: … 7/
Continue reading

Thunderbird logging connection issues for POP3 IMAP and SMTP

I came across an issue where Thunderbird appears to be connecting and using PLAIN TEXT authentication, leaving username and password visible, even though I have Authentication set it to SSL/TLS or STARTTLS.

In order to troubleshoot this issue, I found the following article:

Following the instructions in that article did NOT work!

It says you are supposed to use MOZ_LOG and MOZ_LOG_FILE as of April 2017 however these variables did not work even though it is June 2018. I had to use the old variable names of NSPR_LOG_MODULES and NSPR_LOG_FILE.

The following is the batch file (for Windows 10) that I used and was able to get a log for troubleshooting the authentication and connection to my POP3 and SMTP servers:

set NSPR_LOG_MODULES=negotiateauth:5,POP3:5,SMTP:5,timestamp
set NSPR_LOG_FILE=%USERPROFILE%\Desktop\tb-connect.log
"%ProgramFiles(x86)%\Mozilla Thunderbird\thunderbird.exe"

Using this log I was able to identify that it was indeed using PLAIN TEXT authentication. I am still in the process of trying to determine if this is a Thunderbird bug or a server side bug and will report back with further details when I have them.

I have posted a Bug Report on Thunderbird site in order to track the issue: