LVVTA

 

 

Technical Advisory Committee DEcISION Reporting

The Low Volume Vehicle Technical Association provides a summary of all decisions which have been made by the Technical Advisory Committee (TAC) relating to a request for a variation from an LVVTA Technical Requirement.

The LVV Standards, Information Sheets and the Hobby Car Manual cover the majority of LVV certification needs.

However, because there are many, often innovative, ways a vehicle can be modified, it is not possible to cover every situation in a workable set of documents. The Technical Advisory Committee (TAC) therefore considers designs that are not included in the existing code documentation.

The LVVTA Operating Requirements Schedule (subsection 4.6) outlines the process by which LVV Certifiers identify the need for a TAC application. Variations from technical requirements are approved or rejected by the TAC based on their merits on a case-by-case basis.

Whether an application for variation from technical requirements is approved or declined by the TAC, it will be notified on this page. This notification is intended to help vehicle owners determine if their idea is worth pursuing – if you have a similar modification and wish to apply for a variation from technical requirements, contact an LVV Certifier.

  • * Applications will be notified within two weeks of the date of the TAC meeting.
  • * In line with New Zealand privacy law and LVVTA policy, no commercially sensitive information or applicant details will be published.
  • * If you want to request a previous application, there will be a cost associated with the retrieval and review process, and some details may not be appropriate for release.

 

Meeting Date

September 5th 2017 - 1 variations from Technical Requirement was considered at this meeting

August 1st 2017 - No variations from Technical Requirements were considered at this meeting

July 4th 2017 - No variations from Technical Requirements were considered at this meeting

June 6th 2017 - No variations from Technical Requirements were considered at this meeting

May 2nd 2017 - No variations from Technical Requirements were considered at this meeting

April 4th 2017 - 1 variations from Technical Requirement was considered at this meeting

March 7th 2017 - No variations from Technical Requirements were considered at this meeting

February 7th 2017 - No variations from Technical Requirements were considered at this meeting

January 17th 2017 - No variations from Technical Requirements were considered at this meeting

December 7th 2016 - 1 variation from Technical Requirements was considered at this meeting however details are withheld from public domain for reasons of commercial sensitivity.

December 6th 2016 - No variations from Technical Requirements were considered at this meeting

November 1st 2016 - No variations from Technical Requirements were considered at this meeting

October 4th 2016 - 2 variations from Technical Requirements were considered at this meeting

September 6th 2016 - No variations from Technical Requirements were considered at this meeting

August 3rd 2016 - No variations from Technical Requirements were considered at this meeting

August 2nd 2016 - No variations from Technical Requirements were considered at this meeting

July 5th 2016 - 3 variations from Technical Requirements were considered at this meeting

June 7th 2016 - No variations from Technical Requirements were considered at this meeting

April 28th 2016 - No variations from Technical Requirements were considered at this meeting

April 5th 2016 - No variations from Technical Requirements were considered at this meeting

March 1st 2016 - 2 variations from Technical Requirements were considered at this meeting

February 4th 2016 - No variations from Technical Requirements were considered at this meeting

January 19th 2016 - No variations from Technical Requirements were considered at this meeting